STEP 1
Connect Currents and Sentry
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 Sentry Integration
Keep Currents and Sentry in sync by integrating their events and actions. When developer tools events happen in Currents, update the Sentry 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 Sentry
Detailed info you need to know about Currents and Sentry integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Currents to Sentry
Set up your Currents and Sentry integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Currents and Sentry 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 Sentry. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Currents and Sentry work in WEXTL?
WEXTL exposes actions and triggers for Currents and Sentry 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 triggersSentry 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.
Sentry modules
- Add Organization MemberAdds a member to an organization.
- Add Project Symbol SourceAdds a symbol source to a project.
- Add Project TeamAdds a team to a project.
- Add Team MemberAdds an organization member to a team.
- Create AlertCreates an organization alert.
- Create Client KeyCreates a project client key.
- Create Cron MonitorCreates a cron monitor.
- Create DeployCreates a deploy for a release.
- Create Issue MonitorCreates an issue monitor for a project.
- Create Organization ProjectCreates a project in an organization.
- Create ReleaseCreates an organization release.
- Create Spike ProtectionEnables spike protection for projects.
- Create Spike Protection NotificationCreates a spike protection notification action.
- Create TeamCreates a team.
- Create Team ProjectCreates a project on a team.
- Delete AlertDeletes an alert.
- Delete Client KeyDeletes a client key.
- Delete Cron MonitorDeletes a cron monitor.
- Delete Issue MonitorDeletes an issue monitor.
- Delete Organization MemberRemoves an organization member.
- Delete ProjectDeletes a project.
- Delete Project Release FileDeletes a project release file.
- Delete Project Symbol SourceDeletes a project symbol source.
- Delete Project TeamRemoves a team from a project.
- Delete ReleaseDeletes an organization release.
- Delete Release FileDeletes an organization release file.
- Delete Spike ProtectionDisables spike protection for projects.
- Delete Spike Protection NotificationDeletes a spike protection notification action.
- Delete TeamDeletes a team.
- Delete Team MemberRemoves a member from a team.
- Get AlertReturns an alert.
- Get Client KeyReturns a client key.
- Get Cron MonitorReturns a cron monitor.
- Get Event AttachmentReturns an event attachment.
- Get Event Source Map DebugReturns source-map debug information for an event.
- Get IssueReturns an issue.
- Get Issue EventReturns an issue event.
- Get Issue MonitorReturns an issue monitor.
- Get Issue Tag DetailsReturns tag details for an issue.
- Get OrganizationReturns an organization.
- Get Organization Event CountsReturns organization event counts.
- Get Organization MemberReturns an organization member.
- Get Organization Stats SummaryReturns event counts by project.
- Get ProjectReturns a project.
- Get Project EnvironmentReturns a project environment.
- Get Project EventReturns a project event.
- Get Project Event CountsReturns event counts for a project.
- Get Project OwnershipReturns ownership rules for a project.
- Get Project Release FileReturns a project release file.
- Get ReleaseReturns an organization release.
Frequently asked questions
Common questions about connecting Currents and Sentry.
Connect your Currents and Sentry 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 Organization Member" in Sentry. Currents has 1 trigger (including Watch Events); Sentry has 130 actions (including Add Organization Member, Add Project Symbol Source, and Add Project Team). 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-Sentry 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 Sentry) 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 + Sentry 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 Sentry integration.
- Currents and Sentry integration source code, module specs and credentials implementation.
- Our Currents and Sentry integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Currents and Sentry — 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
- Sentry integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library