Keep billing milestones connected to design
Turn a meaningful billing milestone into a reminder beside the design work it may affect.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Milestones from billing operations can pass without prompting a review of the related customer experience.
- Put a relevant milestone beside the associated design file.
- Prompt a timely review of the customer experience.
- Reduce reliance on remembering to notify design collaborators.
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 tell Notis what should happen when a milestone arrives.
- 3Use one instruction to add a concise comment to the relevant Figma file when your billing service sends a design-relevant milestone.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test with one real milestone and confirm the comment lands in the intended file.
Questions about this workflow
Does Billsby send the Notis trigger itself?
This package has no Billsby trigger events. An external billing service or custom backend must send the webhook to Notis.
Can the workflow choose a file automatically?
Describe how the incoming context identifies the relevant file in the plain-language instruction.
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.