Authenticate requests using your Workflows API credentials, then attach required headers to each call.
Configure Drupal to securely store and transmit your Workflows API credentials with every request.
Primary endpoints include GET /surveys/ and GET /surveys/submissions. Other endpoints can be added as needed.
Trigger: Drupal requests the latest surveys to populate dashboards or content lists.
Actions: Retrieve surveys, map fields, and store in Drupal content or entities.
GET /surveys/
id, title, status, created_at
Trigger: Pull new submissions for each survey as users respond.
Actions: Create or update Drupal entries with respondent data and answers.
GET /surveys/submissions
id, survey_id, respondent, responses, submitted_at
Trigger: Drupal receives real-time webhooks for survey events.
Actions: Trigger immediate updates in Drupal content when data changes.
POST /surveys/webhooks
webhook_id, event, payload
Automate survey retrieval without custom coding.
Keep Drupal content in sync with live survey data.
Secure and centralized authentication for API calls.
A quick glossary of terms used in this integration: endpoints, triggers, actions, and data fields.
A URL path exposed by the Workflows API to perform a specific action.
A callback that notifies Drupal of changes in the Workflows API in real time.
The process of verifying identity to access the Workflows API.
Responses submitted by survey participants.
Automatically publish new surveys from the Workflows API to a Drupal content type or view.
Map submission data to Drupal form submissions or entities for reporting.
Use webhooks to create real-time dashboards in Drupal admin.
Obtain your API key and endpoint URLs from the Workflows API dashboard and note them for config.
Install modules, set up credentials storage, and configure HTTP requests to the endpoints.
Run test calls to endpoints and verify data appears in Drupal with correct mappings.
No-code options exist for basic read-only integrations in this workflow setup. For more advanced scenarios, you may need to add simple module configurations. Consider using pre-built connectors or automation tools that bridge Drupal and the Workflows API without writing server-side code. In most cases you can get started with a few configuration steps.
Start with the endpoints for surveys and submissions to validate data flow. You can later enable additional endpoints as you expand your integration. Testing in a staging environment is recommended.
Authentication typically uses an API key or OAuth token. Store tokens securely in Drupal config and attach them as headers to each request. Rotate credentials regularly.
Yes. Webhooks can push updates to Drupal in real time, enabling dashboards and alerts without polling.
Store credentials in Drupal’s configuration management system or a protected settings file. Use environment variables or a secret manager if available.
Yes, a no-code approach is possible for basic data retrieval and display. For complex workflows, some scripting or a small module can help.
The integration commonly syncs survey id, respondent data, timestamps, and the responses to various questions depending on field mappings.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
