STEP 1
Connect Currents and Oneflow
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 Oneflow Integration
Keep Currents and Oneflow in sync by integrating their events and actions. When developer tools events happen in Currents, update the Oneflow 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 Currents and Oneflow
Detailed info you need to know about Currents and Oneflow integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Currents to Oneflow
Set up your Currents and Oneflow integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Currents and Oneflow 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 Oneflow. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Currents and Oneflow work in WEXTL?
WEXTL exposes actions and triggers for Currents and Oneflow 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 triggersOneflow 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.
Oneflow modules
- Add a Product to a Product GroupAdds a product to a specific product group.
- Copy a ContractCreates a duplicate of an existing contract.
- Create a CommentCreates a comment.
- Create a ContactCreates a new contact in the specified address book or contact list.
- Create a ContractCreates a new contract based on the provided template and data.
- Create a FolderCreates a new folder within the specified directory or service.
- Create a GroupCreates a new group in the specified service.
- Create a LinkCreates a new link in the system.
- Create a ParticipantCreates a participant in the system.
- Create a PartyCreates a new party and adds it to the system.
- Create a ReminderCreates a new reminder in the system.
- Create a TagCreates a tag in the system.
- Create a Template from a ContractCreates a template based on an existing contract.
- Create a UserCreates a user in the system.
- Create an Access LinkGenerates an access link for a specific resource or service.
- Decline a Contract by IDDeclines a contract using its specific ID.
- Delete a Contact by IDDeletes a contact using the ID.
- Delete a ContractDeletes a contract by its ID.
- Delete a Contract LinkDeletes a contract link using the link ID.
- Delete a FolderDeletes a folder using its ID.
- Delete a GroupDeletes a specified group in the system.
- Delete a Participant by IDDeletes a participant using the specific participant ID.
- Delete a PartyDeletes a party by its ID.
- Delete a Product in a Product GroupDeletes a product from a specified product group.
- Delete a Reminder by IDDeletes a reminder using its ID.
- Delete a Tag by IDDeletes a tag identified by its ID.
- Get a Contact by IDRetrieves a contact using its ID.
- Get a Contract by IDRetrieves a contract using its ID.
- Get a Contract CommentRetrieves a contract comment using its ID.
- Get a Contract Data Field by IDRetrieves a contract data field using the specified ID.
- Get a Contract Event by IDRetrieves a contract event using its ID.
- Get a Contract FileRetrieves a contract file using the specified ID.
- Get a GroupRetrieves details of a specified group.
- Get a ParticipantRetrieves a participant using their ID.
- Get a PartyRetrieves a party using the provided ID.
- Get a Product by IDRetrieves a product using its ID.
- Get a Product Group by IDRetrieves a product group using its ID.
- Get a Product in a Product GroupRetrieves a product within a specified product group.
- Get a Reminder by IDRetrieves a reminder using its ID.
- Get a TagRetrieves a tag using its ID.
- Get a Template by IDRetrieves a template by its ID.
- Get a Template File by IDRetrieves a template file using the specified ID.
- Get a UserRetrieves a user from the service.
- Get a WorkspaceRetrieves a workspace using its ID.
- Get Account InformationRetrieves account-related information for the specified user or service.
- Get ContactsRetrieves contacts in a workspace.
- Get Contract Data FieldsRetrieves data fields from a contract.
- Get Contract FilesRetrieves contract files from the service.
- Get ContractsRetrieves details of a specific contract from the service.
- Get FoldersRetrieves folders from the service.
Frequently asked questions
Common questions about connecting Currents and Oneflow.
Connect your Currents and Oneflow 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 a Product to a Product Group" in Oneflow. Currents has 1 trigger (including Watch Events); Oneflow has 87 actions (including Add a Product to a Product Group, Copy a Contract, and Create a Comment). 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-Oneflow 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 Oneflow) 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 + Oneflow 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 Oneflow integration.
- Currents and Oneflow integration source code, module specs and credentials implementation.
- Our Currents and Oneflow integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Currents and Oneflow — 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
- Oneflow integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library