Automate Figma

What Figma is

Figma is a collaborative interface design tool. Its API covers files and their node trees, comments, components, styles, projects and webhooks.

API host: api.figma.com

What HumDay can do in Figma

12 documented operations change something in Figma.

• POSTAdd a comment to a file/v1/files/{file_key}/comments
• POSTCreate a webhook/v2/webhooks
• POSTAdd a reaction to a comment/v1/files/{file_key}/comments/{comment_id}/reactions
• DELETEDelete a comment/v1/files/{file_key}/comments/{comment_id}
• POSTCreate dev resources/v1/dev_resources
• POSTCreate/modify/delete variables/v1/files/{file_key}/variables
• DELETEDelete a reaction/v1/files/{file_key}/comments/{comment_id}/reactions
• DELETEDelete a webhook/v2/webhooks/{webhook_id}
• PUTUpdate a webhook/v2/webhooks/{webhook_id}
• PUTUpdate dev resources/v1/dev_resources
• POSTGet developer logs/v1/developer_logs
• DELETEDelete dev resource/v1/files/{file_key}/dev_resources/{dev_resource_id}

What HumDay can read from Figma

These are the operations a schedule or a trigger can watch.

• GETGet current user/v1/me
• GETGet comments in a file/v1/files/{file_key}/comments
• GETGet file JSON/v1/files/{file_key}
• GETRender images of file nodes/v1/images/{file_key}
• GETGet payments/v1/payments
• GETGet file metadata/v1/files/{file_key}/meta
• GETGet file JSON for specific nodes/v1/files/{file_key}/nodes
• GETGet file styles/v1/files/{file_key}/styles
• GETGet versions of a file/v1/files/{file_key}/versions
• GETGet files in a folder/v2/folders/{folder_id}/files
• GETGet file components/v1/files/{file_key}/components
• GETGet file component sets/v1/files/{file_key}/component_sets
• GETGet reactions for a comment/v1/files/{file_key}/comments/{comment_id}/reactions
• GETGet a webhook/v2/webhooks/{webhook_id}
• GETGet oEmbed data/v1/oembed
• GETGet webhooks by context or plan/v2/webhooks
• GETGet activity logs/v1/activity_logs
• GETGet image fills/v1/files/{file_key}/images
• GETGet folder metadata/v2/folders/{folder_id}/meta
• GETGet subfolders in a folder/v2/folders/{folder_id}/folders
• GETGet dev resources/v1/files/{file_key}/dev_resources
• GETGet webhook requests/v2/webhooks/{webhook_id}/requests
• GETGet daily AI credit usage/v1/ai_usage/daily
• GETGet local variables/v1/files/{file_key}/variables/local
• GETGet style/v1/styles/{key}
• GETGet component/v1/components/{key}
• GETGet published variables/v1/files/{file_key}/variables/published
• GETGet component set/v1/component_sets/{key}
• GETGet team styles/v1/teams/{team_id}/styles
• GETGet top-level folders in a team/v2/teams/{team_id}/folders
• GETGet team components/v1/teams/{team_id}/components
• GETGet team component sets/v1/teams/{team_id}/component_sets
• GETGet library analytics style usage data./v1/analytics/libraries/{file_key}/style/usages
• GETGet library analytics style action data./v1/analytics/libraries/{file_key}/style/actions
• GETGet library analytics variable usage data./v1/analytics/libraries/{file_key}/variable/usages
• GETGet library analytics component usage data./v1/analytics/libraries/{file_key}/component/usages
• GETGet library analytics variable action data./v1/analytics/libraries/{file_key}/variable/actions
• GETGet library analytics component action data./v1/analytics/libraries/{file_key}/component/actions

How automating Figma works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Figma account.
4. Grant access, then go live. You approve the specific Figma operations it may use — and only those.

Popular Figma integrations

Connect Figma to the tools people pair it with most.

• Figma and OData for namespace microsoft.graphintegration
• Figma and Cloudflareintegration
• Figma and NetBoxintegration
• Figma and GitHubintegration
• Figma and Mistintegration
• Figma and Loket.nlintegration
• Figma and Atlassian The Jira Cloud platformintegration
• Figma and Magento B2Bintegration
• Figma and Stripeintegration
• Figma and Zuora Reference Billingintegration
• Figma and bunqintegration
• Figma and DocuSignintegration

Automate Figma with these

• GitHub811 operations
• Trello324 operations
• Bitbucket292 operations
• Orthanc Server Orthanc268 operations
• Asana249 operations
• Discord242 operations
• Slack174 operations
• Visualstudio VSOnline152 operations
• OnSched Setup138 operations
• StackExchange124 operations
• Slicebox118 operations
• Noosh application102 operations

Categories

• Collaboration
• Tools

Questions about Figma automation

Can HumDay connect to Figma?

Yes. HumDay reads Figma's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 50 operations are documented.

Do I need to write code to automate Figma?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Figma account.

What can HumDay do in Figma?

12 of the 50 documented operations change something in Figma, and 38 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Figma account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Figma is held behind that approval.

Where this came from

The operations above are read from the API description Figma publishes themselves at raw.githubusercontent.com/figma/rest-api-spec/main/openapi/openapi.yaml. Descriptions are the provider’s own words, not ours.