Stay oriented on billing design activity
Replace scattered check-ins with one scheduled summary of recent Figma activity.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get activity logs
Retrieves activity log events from figma, allowing filtering by event types, time range, and pagination.
Why this helps
Frequent context switches make it easy to miss what changed in a billing design file or team.
- Review activity in a regular, predictable window.
- Catch up without repeatedly checking Figma.
- Keep design changes connected to billing work.
Setup
Build it in a few focused steps.
- 1Connect Billsby and Figma to Notis once in the portal.
- 2Create an automation or ask Notis for a recurring activity digest in plain language.
- 3In one instruction, ask Notis to retrieve recent Figma activity relevant to subscription and billing design and summarize it.
- 4Pick a schedule and choose the channel for run reports.
- 5Test once and confirm the digest is useful and appropriately scoped.
Questions about this workflow
Can Notis guarantee every activity is a billing change?
No. The activity log is retrieved from Figma; the instruction should ask Notis to focus its summary on relevant billing design activity.
What starts the digest?
A Notis recurring schedule starts it; Billsby trigger events are not available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Billsby to Figma. A trigger fires from one place; an action lands in another.
Billsby triggers
Figma actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a comment to a file
Posts a new comment to a figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region height` and `region width` in `client meta` must be positive if defining a comment region.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a reaction to a comment
Posts a specified emoji reaction to an existing comment in a figma file or branch, requiring valid file key and comment id.
Create a webhook
Creates a figma webhook for a `team id` to send post notifications for an `event type` to a publicly accessible https `endpoint`; an initial ping is sent unless `status` is `paused`.
Create dev resources
Creates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node.
Create, modify, or delete variables
Manages variables, collections, modes, and their values in a figma file via batch create/update/delete operations; use temporary ids to link new related items in one request and ensure `variablemodevalues` match the target variable's `resolvedtype`.
Delete a comment
Deletes a specific comment from a figma file or branch, provided the authenticated user is the original author of the comment.
Delete a reaction
Deletes a specific emoji reaction from a comment in a figma file; the user must have originally created the reaction.
Delete a webhook
Permanently deletes an existing webhook, identified by its unique `webhook id`; this operation is irreversible.
Connect any two apps with Notis in the middle.
Billsby and Figma, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Figma.