STEP 1
Connect Bitwarden 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.
Bitwarden and Currents Integration
Connect Bitwarden and Currents 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 Bitwarden and Currents
Detailed info you need to know about Bitwarden and Currents integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Bitwarden to Currents
Set up your Bitwarden and Currents integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Bitwarden 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 Bitwarden and Currents. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Bitwarden and Currents work in WEXTL?
WEXTL exposes actions and triggers for Bitwarden 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.
Currents triggersBitwarden 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 ActionsRetrieves the actions configured for a project.
- List Action Test ExecutionsRetrieves the test executions where one action was applied.
- 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 ProjectsRetrieves the projects in your Currents organization.
- List Project TermsRetrieves the filter terms of one kind recorded for a project.
- 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.
Bitwarden modules
- Create GroupCreates a new organization group.
- Delete CollectionPermanently deletes an organization collection.
- Delete GroupDeletes an organization group.
- Get CollectionReturns a single organization collection.
- Get GroupReturns a single organization group.
- Get MemberReturns a single organization member.
- Import OrganizationBulk-imports members and groups from a directory.
- Invite MemberInvites a new member to the organization.
- List CollectionsRetrieves a list of organization collections.
- List EventsRetrieves organization audit events.
- List GroupsRetrieves a list of organization groups.
- List MembersRetrieves a list of organization members.
- List PoliciesRetrieves organization policies.
- Make an API CallPerforms an arbitrary authorized API call.
- Remove MemberRemoves a member from the organization.
- Set Group MembersReplaces the member roster of a group.
- Update CollectionUpdates collection access associations.
- Update GroupUpdates an organization group.
- Update MemberUpdates an organization member.
- Update PolicyUpdates an organization policy.
Frequently asked questions
Common questions about connecting Bitwarden and Currents.
Connect your Bitwarden 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 Currents's "Watch Events" fires, WEXTL can "Create Group" in Bitwarden. Bitwarden has 20 actions (including Create Group, Delete Collection, and Delete Group); 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. Bitwarden-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 Bitwarden (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 Bitwarden + 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 Bitwarden and Currents integration.
- Bitwarden and Currents integration source code, module specs and credentials implementation.
- Our Bitwarden and Currents integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Bitwarden 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.
- Bitwarden integration information
- Currents integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library