STEP 1
Connect Currents and GitHub
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 GitHub Integration
Build developer tools workflows between Currents and GitHub 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 Currents and GitHub
Detailed info you need to know about Currents and GitHub integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Currents to GitHub
Set up your Currents and GitHub integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Currents and GitHub 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 GitHub. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Currents and GitHub work in WEXTL?
WEXTL exposes actions and triggers for Currents and GitHub 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 triggersGitHub 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.
GitHub modules
- Accept a Repository InvitationPerforms the a Repository Invitation operation.
- Add a Dependency an Issue Is Blocked byAdds a dependency an issue is blocked by.
- Add a Field to an Organization-owned ProjectAdds a field to an organization-owned project.
- Add a Repository CollaboratorAdds a Repository Collaborator.
- Add a Repository to the List of Repositories Allowed to Use Self-hosted Runners in an OrganizationAdds a Repository to the List of Repositories Allowed to Use Self-hosted Runners in an Organization.
- Add a Self-hosted Runner to a Group for an OrganizationAdds a Self-hosted Runner to a Group for an Organization.
- Add an Email Address for the Authenticated UserAdds an email address for the authenticated user.
- Add App Access RestrictionsAdds app access restrictions.
- Add Assignees to an IssueAdds assignees to an issue.
- Add Custom Labels to a Self-hosted Runner for a RepositoryAdds custom labels to a self-hosted runner for a repository.
- Add Custom Labels to a Self-hosted Runner for an OrganizationAdds custom labels to a self-hosted runner for an organization.
- Add Field to User Owned ProjectAdds field to user owned project.
- Add Issue Field Values to an IssueAdds issue field values to an issue.
- Add Item to Organization Owned ProjectAdds item to organization owned project.
- Add Item to User Owned ProjectAdds item to user owned project.
- Add Labels to an IssueAdds labels to an issue.
- Add or Update Team Membership for a UserAdds or Update Team Membership for a User.
- Add or Update Team Membership for a User (Legacy)Adds or Update Team Membership for a User (Legacy).
- Add or Update Team Repository PermissionsAdds or Update Team Repository Permissions.
- Add or Update Team Repository Permissions (Legacy)Adds or Update Team Repository Permissions (Legacy).
- Add Pull Requests to a Pull Request StackAdds pull requests to a pull request stack.
- Add Repository Access to a Self-hosted Runner Group in an OrganizationAdds repository Access to a Self-hosted Runner Group in an Organization.
- Add Selected Repository to an Organization SecretAdds selected Repository to an Organization Secret.
- Add Selected Repository to an Organization SecretAdds selected Repository to an Organization Secret.
- Add Selected Repository to an Organization VariableAdds selected Repository to an Organization Variable.
- Add Social Accounts for the Authenticated UserAdds social accounts for the authenticated user.
- Add Status Check ContextsAdds status check contexts.
- Add Sub-issueAdds sub-issue on GitHub.
- Add Team Access RestrictionsAdds team access restrictions.
- Add Team Member (Legacy)Adds team Member (Legacy).
- Add User Access RestrictionsAdds user access restrictions.
- Approve a Workflow Run for a Fork Pull RequestApproves a Workflow Run for a Fork Pull Request.
- Approve an Issue SuggestionApproves an Issue Suggestion.
- Block a UserPerforms the a User operation.
- Block a User from an OrganizationPerforms the a User from an Organization operation.
- Bulk Create Organization Custom PatternsPerforms the create Organization Custom Patterns operation.
- Bulk Create Repository Custom PatternsPerforms the create Repository Custom Patterns operation.
- Bulk Delete Organization Custom PatternsBulk deletes organization custom patterns.
- Bulk Delete Repository Custom PatternsBulk deletes repository custom patterns.
- Cancel a GitHub Pages DeploymentCancels a GitHub Pages Deployment.
- Cancel a Workflow RunCancels a Workflow Run.
- Cancel an Organization InvitationCancels an organization invitation.
- Check If a Gist Is StarredReturns whether a gist is starred.
- Check If a Person Is Followed by the Authenticated UserReturns whether a person is followed by the authenticated user.
- Check If a Pull Request Has Been MergedReturns whether a pull request has been merged.
- Check If a Repository Is Starred by the Authenticated UserReturns whether a repository is starred by the authenticated user.
- Check If a User Can Be AssignedReturns whether a user can be assigned to a repository.
- Check If a User Can Be Assigned to a IssueReturns whether a user can be assigned to an issue.
- Check If a User Follows Another UserReturns whether a user follows another user.
- Check If a User Is a Repository CollaboratorReturns whether a user is a repository collaborator.
Frequently asked questions
Common questions about connecting Currents and GitHub.
Connect your Currents and GitHub 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 "Accept a Repository Invitation" in GitHub. Currents has 1 trigger (including Watch Events); GitHub has 811 actions (including Accept a Repository Invitation, Add a Dependency an Issue Is Blocked by, and Add a Field to an Organization-owned Project). 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-GitHub 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 GitHub) 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 + GitHub 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 GitHub integration.
- Currents and GitHub integration source code, module specs and credentials implementation.
- Our Currents and GitHub integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Currents and GitHub — 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
- GitHub integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library