STEP 1
Connect Agenty 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.
Agenty and Currents Integration
Build developer tools workflows between Agenty and Currents on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Agenty and Currents
Detailed info you need to know about Agenty and Currents integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Agenty to Currents
Set up your Agenty and Currents integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Agenty 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 Agenty and Currents. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Agenty and Currents work in WEXTL?
WEXTL exposes actions and triggers for Agenty 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.
Agenty triggersCurrents actions
Agenty modules
- Watch Agent JobsTriggers when an agent job completes or fails.
- Add Agents to a ProjectAdds one or more agents to a project.
- Add Rows to a ListAdds one or more rows to a stored list.
- Cancel a Running JobStops a job that is currently running.
- Change Agent Schedule StatusEnables or disables an agent's existing schedule.
- Change API Key StatusChanges whether an API key can authenticate requests.
- Change Workflow StatusEnables or disables an automation in your Agenty account.
- Copy an AgentCreates a copy of an existing agent.
- Create a ListCreates a new stored list.
- Create a ProjectCreates a new project.
- Create a WorkflowCreates an automation in your Agenty account that runs when a job completes.
- Create an AgentCreates a new scraping, crawling or monitoring agent.
- Create an API KeyCreates a new API key for the account.
- Delete a ConnectionRemoves a stored OAuth grant from the account.
- Delete a ListPermanently deletes a stored list by its id.
- Delete a List RowPermanently deletes a single row from a stored list.
- Delete a WorkflowPermanently deletes an automation from your Agenty account.
- Delete Agent ScheduleRemoves the run schedule from an agent.
- Delete Agents by IdPermanently deletes one or more agents by their ids.
- Delete an AgentPermanently deletes a single agent by its id.
- Delete an API KeyPermanently deletes an API key from the account.
- Delete Projects by IdPermanently deletes one or more projects by their ids.
- Delete Rows by IdDeletes selected rows from a list by their ids.
- Delete Users by IdPermanently deletes one or more team members by their ids.
- Download API Keys as CSVDownloads the account's API keys as a CSV file.
- Download Job ResultDownloads a job's extracted result as a file.
- Download Jobs as CSVDownloads the account's jobs as a CSV file.
- Download List Rows as CSVDownloads the rows of a list as a CSV file.
- Get a JobReturns a single job by its id.
- Get a ListReturns a single stored list by its id.
- Get a List RowReturns a single row from a stored list.
- Get a ProjectReturns a single project and its associated agents.
- Get a UserReturns a single team member by id.
- Get a WorkflowReturns a single automation from your Agenty account.
- Get Account Usage ReportReturns how many pages the account has used over a date range.
- Get Agent InputReturns the input source configured on an agent.
- Get Agent ScheduleReturns the schedule configured on an agent.
- Get an AgentReturns a single agent by its id.
- Get an API KeyReturns a single API key by id.
- Get Job Output FileReturns a named output file from a completed job.
- Get Job ResultRetrieves the extracted result rows for a job.
- Get Latest Agent ResultRetrieves the latest result rows for an agent.
- Get ListsRetrieves the stored lists in the account.
- Invite a UserInvites a new team member to the Agenty account.
- List AgentsRetrieves a list of scraping, crawling and monitoring agents in the account.
- List API KeysRetrieves the API keys in the account.
- List ConnectionsRetrieves the stored OAuth connections in the account.
- List Job LogsRetrieves the log lines recorded for a job.
- List JobsRetrieves a list of agent jobs in the account.
- List ProjectsRetrieves the projects in the account.
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 Agenty and Currents.
Connect your Agenty 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 Agenty's "Watch Agent Jobs" fires, WEXTL can "Cancel Run" in Currents. Agenty has 1 trigger (including Watch Agent Jobs); 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. Agenty-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 Agenty (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 Agenty + 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 Agenty and Currents integration.
- Agenty and Currents integration source code, module specs and credentials implementation.
- Our Agenty and Currents integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Agenty 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.
- Agenty integration information
- Currents integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library