STEP 1
Connect Currents and Figma
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Currents and Figma Integration
Connect Currents and Figma to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Currents and Figma
Detailed info you need to know about Currents and Figma integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Currents to Figma
Set up your Currents and Figma integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Currents and Figma nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Currents and Figma. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Currents and Figma work in WEXTL?
WEXTL exposes actions and triggers for Currents and Figma that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Currents triggersFigma actions
Currents modules
- Cancel RunCancels a run that is still in progress.
- Cancel Run by GitHub CICancels a run identified by its GitHub Actions workflow run.
- Create ActionCreates a new action that quarantines, skips, or tags matching tests.
- Create Jira IssueCreates a Jira issue from a test in a run and links it back.
- Delete ActionArchives an action so it stops applying to tests.
- Delete Project TermDeletes a tag term from a project's filter list.
- Delete RunDeletes a run and all of its associated data.
- Disable ActionDisables an action without archiving it.
- Enable ActionEnables an action that is currently disabled.
- Find RunReturns the most recent completed run matching the criteria.
- Generate Test SignatureComputes the stable signature for a test from its project, spec file, and title.
- Get ActionReturns a single action by its identifier.
- Get Affected Test ExecutionsRetrieves the executions of one affected test in a date range.
- Get InstanceReturns a single spec-file instance with its test results.
- Get ProjectReturns a single project by its identifier.
- Get Project InsightsReturns aggregated run and test metrics for a project.
- Get RunReturns a single run with its groups and spec results.
- Get Test Failure ContextReturns structured failure context for a run, a spec file, or a single test.
- Get Test ResultsRetrieves the historical executions of one test signature.
- Get WebhookReturns a single webhook by its identifier.
- Link Jira IssueLinks an existing Jira issue to a test in a run.
- List Action Test ExecutionsRetrieves the test executions where one action was applied.
- List ActionsRetrieves the actions configured for a project.
- List Affected TestsRetrieves the tests affected by actions in a date range.
- List ErrorsRetrieves errors from the Errors Explorer for a project.
- List Jira Issue TypesRetrieves the Jira issue types available for a Jira project.
- List Jira ProjectsRetrieves the Jira projects available to the connected Jira integration.
- List Project RunsRetrieves the test runs recorded for a project.
- List Project TermsRetrieves the filter terms of one kind recorded for a project.
- List ProjectsRetrieves the projects in your Currents organization.
- List Pull RequestsRetrieves the pull requests with run activity for a project.
- List Spec FilesRetrieves spec files from the Spec Files Explorer for a project.
- List TestsRetrieves tests from the Tests Explorer for a project.
- List WebhooksRetrieves the webhooks configured for a project.
- Make an API CallPerforms an arbitrary authorized API call.
- Reset RunResets failed spec files in a run so they can run again.
- Update ActionUpdates an existing action.
- Update WebhookUpdates the URL, events, headers, or label of a webhook.
- Watch EventsTriggers when a test run starts, finishes, times out, or is cancelled.
Figma modules
- Add Comment ReactionAdds a reaction to a comment.
- Create CommentCreates a comment on a file.
- Create Dev ResourcesCreates dev resources.
- Delete CommentDeletes a comment on a file.
- Delete Comment ReactionDeletes a reaction from a comment.
- Delete Dev ResourceDeletes a dev resource.
- Get ComponentReturns a published component by key.
- Get Component SetReturns a published component set by key.
- Get Current UserReturns the currently authenticated user.
- Get Developer LogsRetrieves developer logs for debugging API integration.
- Get FileRetrieves the JSON representation of a Figma file.
- Get File ImagesRetrieves image fill URLs for a file.
- Get File MetadataReturns metadata for a Figma file.
- Get File NodesRetrieves specific nodes from a Figma file.
- Get Folder MetadataReturns metadata for a folder.
- Get Library Component Action AnalyticsRetrieves component action analytics for a library file.
- Get Library Component Usage AnalyticsRetrieves component usage analytics for a library file.
- Get Library Style Action AnalyticsRetrieves style action analytics for a library file.
- Get Library Style Usage AnalyticsRetrieves style usage analytics for a library file.
- Get Library Variable Action AnalyticsRetrieves variable action analytics for a library file.
- Get Library Variable Usage AnalyticsRetrieves variable usage analytics for a library file.
- Get Local VariablesRetrieves local variables in a file.
- Get OEmbed MetadataRetrieves oEmbed metadata for a Figma file or prototype URL.
- Get Payment StatusRetrieves payment status for a community file.
- Get Project MetadataReturns metadata for a project.
- Get Published VariablesRetrieves published variables in a file.
- Get StyleReturns a published style by key.
- Get WebhookRetrieves details of a specific webhook.
- List Activity LogsRetrieves activity logs for your organization.
- List Comment ReactionsRetrieves reactions on a comment. Note: only the first page of reactions is returned.
- List Daily AI UsageRetrieves daily AI usage statistics.
- List Dev ResourcesRetrieves dev resources linked to a file.
- List File CommentsRetrieves comments on a file.
- List File Component SetsRetrieves component sets in a file.
- List File ComponentsRetrieves components in a file.
- List File StylesRetrieves styles in a file.
- List File VersionsRetrieves version history for a file.
- List Folder FilesRetrieves files in a folder.
- List Project FilesRetrieves files in a project.
- List SubfoldersRetrieves subfolders in a folder.
- List Team Component SetsRetrieves published component sets in a team.
- List Team ComponentsRetrieves published components in a team.
- List Team FoldersRetrieves top-level folders in a team.
- List Team ProjectsRetrieves projects in a team.
- List Team StylesRetrieves published styles in a team.
- List Team WebhooksRetrieves all webhooks for a specific team.
- List Webhook RequestsRetrieves the request history for a specific webhook.
- List WebhooksRetrieves all webhooks associated with a team or organization. Only the first page is returned when a context filter is present.
- Make an API CallPerforms an arbitrary authorized API call.
- Modify File VariablesCreates, updates, or deletes variables in a file.
Frequently asked questions
Common questions about connecting Currents and Figma.
Connect your Currents and Figma accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Currents's "Watch Events" fires, WEXTL can "Add Comment Reaction" in Figma. Currents has 1 trigger (including Watch Events); Figma has 53 actions (including Add Comment Reaction, Create Comment, and Create Dev Resources). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Currents-to-Figma automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Currents (or Figma) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Currents + Figma automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Currents and Figma integration.
- Currents and Figma integration source code, module specs and credentials implementation.
- Our Currents and Figma integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Currents and Figma — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Currents integration information
- Figma integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library