Understand the billing component before you reuse it
Bring a component's structure back into view before adapting it for another subscription flow.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get component
Get component data with automatic simplification. returns clean, ai-friendly component structure.
Why this helps
Component details can be easy to forget, leading to repeated inspection before a design task can move forward.
- Make a component's structure easier to recall.
- Reduce repeated inspection during design work.
- Help keep subscription screens consistent.
Setup
Build it in a few focused steps.
- 1Connect Billsby and Figma to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to review a component on a schedule.
- 3Tell Notis which billing component to retrieve and ask for a short structure recap.
- 4Choose a recurring schedule and a channel for run reports.
- 5Test with a real component used in subscription design.
Questions about this workflow
Does this create or modify the component?
No. The action retrieves simplified component data.
Can Notis discover the component identifier from a URL?
Use the Figma resource-discovery action separately when you need to find file or node identifiers.
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.