Skip to content
Per-pair page

Connect Figma to HubSpot in two minutes.

Real-time triggers from Figma, ready-made actions in HubSpot. Filter, transform, and route without writing a line of code.

Trigger app
Figma as the trigger

Workflows fire when something happens in Figma.

Action app
HubSpot as the action

Workflows do something in HubSpot, instantly.

See all 23 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

FigmaHubSpot

When something happens in Figma, do it in HubSpot.

3 Figma triggers wired to 23 HubSpot actions. Most-used pairing: Figma Comment AddedCreate Company.

HubSpotFigma

Or fire it the other way around.

18 HubSpot triggers wired to 3 Figma actions downstream.

See HubSpotFigma
Popular pairings

Common Figma → HubSpot workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 69 combinations
When figma comment added in Figma, create company in HubSpot.

Fires when a comment is posted on a Figma file (new thread or reply). The design-review hook — auto-post to #design-review Slack, create a Linear issue if comment matches bug pattern.

When figma comment added in Figma, create contact in HubSpot.

Fires when a comment is posted on a Figma file (new thread or reply). The design-review hook — auto-post to #design-review Slack, create a Linear issue if comment matches bug pattern.

When figma comment added in Figma, create deal in HubSpot.

Fires when a comment is posted on a Figma file (new thread or reply). The design-review hook — auto-post to #design-review Slack, create a Linear issue if comment matches bug pattern.

When figma comment added in Figma, create note in HubSpot.

Fires when a comment is posted on a Figma file (new thread or reply). The design-review hook — auto-post to #design-review Slack, create a Linear issue if comment matches bug pattern.

When figma file updated in Figma, create company in HubSpot.

Fires (debounced ~30s) on any file edit. Useful for "design changed → re-export assets" or "design touched → notify the engineer who built the matching component" workflows. No diff in payload — workflows that need the change run Get File and compare.

When figma file updated in Figma, create contact in HubSpot.

Fires (debounced ~30s) on any file edit. Useful for "design changed → re-export assets" or "design touched → notify the engineer who built the matching component" workflows. No diff in payload — workflows that need the change run Get File and compare.

When figma file updated in Figma, create deal in HubSpot.

Fires (debounced ~30s) on any file edit. Useful for "design changed → re-export assets" or "design touched → notify the engineer who built the matching component" workflows. No diff in payload — workflows that need the change run Get File and compare.

When figma file updated in Figma, create note in HubSpot.

Fires (debounced ~30s) on any file edit. Useful for "design changed → re-export assets" or "design touched → notify the engineer who built the matching component" workflows. No diff in payload — workflows that need the change run Get File and compare.

When figma version created in Figma, create company in HubSpot.

Fires when a designer saves a named version — the discrete handoff moment. The hook for design-to-engineering automation: when v1.0 is saved, auto-create the engineering issue, post the version link to the team.

How it works

Connect Figma and HubSpot in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Figma and HubSpot

    Open Tiny Command, authorize Figma and HubSpot once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Figma trigger

    Drop the Figma → Figma Comment Added trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/figma.trigger-comment-added
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the HubSpot action

    Drop the HubSpot → Create Company action below it. Map fields from the Figma payload into the HubSpot inputs.

    hubspot.create-company
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Figma + HubSpot.

How long does it take to connect Figma and HubSpot on Tiny Command?
Under two minutes. Authorize Figma and HubSpot once each, drop the Figma trigger and HubSpot action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Figma ↔ HubSpot integration real-time?
Yes. Both Figma and HubSpot expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Figma and HubSpot?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit HubSpot.
What Figma events can trigger a HubSpot workflow?
Any of the 3 Figma triggers, including "Figma Comment Added". Each fires in real time when the matching event happens in Figma.
Do I need a paid plan to use Figma with HubSpot?
No. There's a free tier that covers most Figma+HubSpot use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want HubSpot → Figma instead?
Build it the same way, in reverse. There's a dedicated /integrations/hubspot/with/figma page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Figma.


Wire Figma to HubSpot in 2 minutes.

Free tier available. No credit card. No onboarding call.