STEP 1
Connect CircleCI and Currents
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
CircleCI and Currents Integration
Keep CircleCI and Currents in sync by integrating their events and actions. When developer tools events happen in CircleCI, update the Currents automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about CircleCI and Currents
Detailed info you need to know about CircleCI and Currents integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect CircleCI to Currents
Set up your CircleCI and Currents integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected CircleCI and Currents 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 CircleCI and Currents. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between CircleCI and Currents work in WEXTL?
WEXTL exposes actions and triggers for CircleCI and Currents 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.
CircleCI triggersCurrents actions
CircleCI modules
- Watch Workflow & Job EventsTriggers when a workflow or job completes in CircleCI.
- Add Environment VariableCreates environment variable.
- Cancel Job by IDCancels job by id.
- Cancel Job by NumberCancels job by number.
- Cancel WorkflowCancels workflow.
- Continue PipelineContinues pipeline.
- Create Checkout KeyCreates checkout key.
- Create ContextCreates context.
- Create EnvvarCreates envvar.
- Create GroupCreates group.
- Create OrganizationCreates organization.
- Create OTLP ExporterCreates otlp exporter.
- Create Pipeline DefinitionCreates pipeline definition.
- Create Policy BundleCreates policy bundle.
- Create Project in OrgCreates project in org.
- Create RestrictionCreates restriction.
- Create ScheduleCreates schedule.
- Create TriggerCreates trigger.
- Create URL Orb Allow-list EntryCreates url orb allow-list entry.
- Create Usage ExportCreates usage export.
- Create WebhookManually creates an outbound webhook subscription in CircleCI. For the platform's own trigger lifecycle (auto-managed attach/detach), use the Watch Workflow & Job Events trigger instead — using both for the same URL double-subscribes it.
- Delete Checkout KeyDeletes checkout key.
- Delete ContextDeletes context.
- Delete Environment VariableDeletes environment variable.
- Delete EnvvarDeletes envvar.
- Delete GroupDeletes group.
- Delete Org OIDC ClaimsDeletes org oidc claims.
- Delete OrganizationDeletes organization.
- Delete OTLP ExporterDeletes otlp exporter.
- Delete Pipeline DefinitionDeletes pipeline definition.
- Delete ProjectDeletes project.
- Delete Project OIDC ClaimsDeletes project oidc claims.
- Delete RestrictionDeletes restriction.
- Delete ScheduleDeletes schedule.
- Delete TriggerDeletes trigger.
- Delete URL Orb Allow-list EntryDeletes url orb allow-list entry.
- Delete WebhookManually deletes an outbound webhook subscription in CircleCI. Do not use this to remove a Watch Workflow & Job Events trigger's own subscription — removing/deactivating that trigger node detaches it automatically; deleting its webhook here directly leaves the trigger node pointing at a subscription CircleCI no longer has.
- Get Checkout KeyReturns checkout key.
- Get ComponentReturns component.
- Get ContextReturns context.
- Get Context RestrictionsReturns context restrictions.
- Get Current UserReturns current user.
- Get Decision Audit LogsReturns decision audit logs.
- Get Decision by IDReturns decision by id.
- Get Decision SettingsReturns decision settings.
- Get EnvironmentReturns environment.
- Get EnvvarReturns envvar.
- Get GroupReturns group.
- Get JobReturns job.
- Get My PipelinesReturns my pipelines.
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.
Frequently asked questions
Common questions about connecting CircleCI and Currents.
Connect your CircleCI and Currents 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 CircleCI's "Watch Workflow & Job Events" fires, WEXTL can "Cancel Run" in Currents. CircleCI has 1 trigger (including Watch Workflow & Job Events); Currents has 38 actions (including Cancel Run, Cancel Run by GitHub CI, and Create Action). 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. CircleCI-to-Currents 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 CircleCI (or Currents) 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 CircleCI + Currents 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 CircleCI and Currents integration.
- CircleCI and Currents integration source code, module specs and credentials implementation.
- Our CircleCI and Currents integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for CircleCI and Currents — 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.
- CircleCI integration information
- Currents integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library