Skip to content
Notis

Keep shared subscription styles easy to find

Bring the team's published styles back into view before the next billing design task.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Action

Get team styles

Retrieves a paginated list of published styles, such as colors or text attributes, from a specified figma team's library.

Why this helps

Repeatedly hunting through shared styles adds friction to work that already competes for limited attention.

  • Refresh awareness of styles published by the team.
  • Support consistent design across billing screens.
  • Reduce repeated browsing through the style library.

Setup

Build it in a few focused steps.

  • 1Connect Billsby and Figma to Notis once in the portal.
  • 2Create an automation or tell Notis to refresh the style catalog on a recurring basis.
  • 3Ask Notis to retrieve published styles from the Figma team library and summarize those useful for billing design.
  • 4Select a recurring schedule and a channel for run reports.
  • 5Test with a team that has published styles.

Questions about this workflow

Does this retrieve styles from a single file?

This action retrieves published styles from a Figma team.

Does it make design changes?

No. The workflow retrieves style information for review.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

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`.

ActionInstant

Create dev resources

Creates and attaches multiple uniquely-urled development resources to specified figma nodes, up to 10 per node.

ActionInstant

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`.

ActionInstant

Delete a comment

Deletes a specific comment from a figma file or branch, provided the authenticated user is the original author of the comment.

ActionInstant

Delete a reaction

Deletes a specific emoji reaction from a comment in a figma file; the user must have originally created the reaction.

ActionInstant

Delete a webhook

Permanently deletes an existing webhook, identified by its unique `webhook id`; this operation is irreversible.

ActionInstant

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.