Drupal currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Polling by ID
A trigger that polls the Drupal site by ID.
Polling by timestamp
A trigger that polls the Drupal site by timestamp.
Webhook
A webhook that the Drupal site can call to trigger a flow.
Call Service
Call a service on the Drupal site
Create Entity
Create a new entity in Drupal with smart field discovery and validation
List Entities
List entities from Drupal using JSON:API
Get Entity
Retrieve a single entity by UUID
Update Entity
Update an existing entity in Drupal with smart field discovery and validation
Delete Entity
Delete an entity from Drupal
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Drupal event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Polling by ID
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Drupal action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Call Service
Combine Drupal with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
Polling by ID
Finishes with
Call Service, then preserve the outcome in Coherence
The exact authentication fields depend on Drupal. The workflow structure stays straightforward:
Authorize the Drupal account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Drupal or provide a complementary trigger or action.
Drupal currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Drupal currently lists 3 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Drupal triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
