STEP 1
Connect Contentful 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.
Contentful and Currents Integration
Connect Contentful 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 Contentful and Currents
Detailed info you need to know about Contentful and Currents integrations in WEXTL. Explore which modules apps support and how you connect them.
Contentful
Headless CMS content management — spaces, entries, assets, content types, locales, and publishing workflows. [5]
How to connect Contentful to Currents
Set up your Contentful and Currents integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Contentful 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 Contentful and Currents. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Contentful and Currents work in WEXTL?
WEXTL exposes actions and triggers for Contentful 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.
Contentful triggersCurrents actions
Contentful modules
- Activate a Content TypeActivates a content type for delivery.
- Archive an AssetArchives an asset.
- Archive an EntryArchives an entry.
- Archive ReleaseArchives a release.
- Cancel a Scheduled ActionCancels a pending scheduled action.
- Create a CommentCreates a new comment.
- Create a Content Type with POSTCreates a new content type.
- Create a Delivery API KeyCreates a new delivery API key.
- Create a LocaleCreates a new locale.
- Create a New App BundleCreates a new new app bundle.
- Create a New App DefinitionCreates a new new app definition.
- Create a Personal Access TokenCreates a new personal access token.
- Create a Preview EnvironmentCreates or updates a preview environment.
- Create a Preview EnvironmentCreates a new preview environment.
- Create a RoleCreates a new role.
- Create a Scheduled Action for a Compose PageCreates a new scheduled action for a compose page.
- Create a Signed RequestCreates a new signed request.
- Create a SpaceCreates a new space.
- Create a Space MembershipCreates a new space membership.
- Create a TaskCreates a new task.
- Create a Workflow DefinitionCreates a new workflow definition.
- Create an ActionCreates a new action.
- Create an AssetCreates a new asset.
- Create an Asset KeyCreates a new asset key.
- Create an EntryCreates a new entry.
- Create an Environment from a Specified EnvironmentCreates a new environment from a specified environment.
- Create an Environment TemplateCreates a new environment template.
- Create an ExtensionCreates a new extension.
- Create One Access GrantCreates a new access Grant.
- Create or Overwrite the App Signing SecretCreates or overwrites the app signing secret.
- Create or Update App DetailsCreates or updates app details.
- Create ReleaseCreates a new release.
- Create Validation Release ActionCreates a validation action for a release.
- Create/update a WebhookCreates or updates a webhook definition.
- Create/update an AssetCreates or updates an asset.
- Create/Update an Environment AliasCreates or updates an environment alias.
- Create/update an ExtensionCreates or updates an extension.
- Creating an App UploadCreates a new app upload resource.
- Creating an Upload ResourceCreates a new upload resource.
- Deactivate a Content TypeDeactivates a published content type.
- Delete a CommentDeletes a comment.
- Delete a Content TypeDeletes a content type.
- Delete a Preview EnvironmentDeletes a preview environment.
- Delete a Single Delivery API KeyDeletes a single Delivery API key.
- Delete a Single RoleDeletes a single role.
- Delete a Single Space MembershipDeletes a single space membership.
- Delete a SpaceDeletes a space.
- Delete a TagDeletes a tag.
- Delete a TaskDeletes a task.
- Delete a Workflow DefinitionDeletes a workflow definition.
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.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Contentful and Currents integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Contentful and Currents.
Connect your Contentful 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 Contentful's "Watch Entries" fires, WEXTL can "Cancel Run" in Currents. Contentful has 2 triggers (including Watch Entries and Watch Webhook Events); 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. Contentful-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 Contentful (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 Contentful + 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 Contentful and Currents integration.
- Contentful and Currents integration source code, module specs and credentials implementation.
- Our Contentful and Currents integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Contentful 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.
- Contentful integration information
- Currents integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library