Use your Workflows API credentials to authorize requests from Acumbamail. Protect keys and rotate regularly.
Generate an API key in Acumbamail and paste it into the connector to authorize data transfers with Workflows API
Endpoints you can leverage include GET /surveys/ to fetch surveys and GET /surveys/submissions to retrieve submissions. Additional endpoints are available as needed
Trigger when a new Acumbamail survey is created
Create or update a Workflows item, trigger follow ups and notify teams
GET /surveys/
survey_id, title, created_at, status
Trigger when a survey submission is received in Acumbamail
Create or update a contact, log submission, and start related workflows
GET /surveys/submissions
survey_id, submission_id, respondent_email
Trigger when a response meets a condition in Acumbamail surveys
GET /surveys/{survey_id}/submissions
survey_id, submission_id, respondent_email, score
Automate data flow between Acumbamail surveys and Workflows without writing code
Eliminate manual data entry and speed up marketing actions
Gain real time insights and better audience segmentation
This glossary explains endpoints triggers actions and fields used when connecting Acumbamail with Workflows API
The application programming interface that enables integration points for automations with Workflows API
A specific URL that exposes a function for retrieving or manipulating data
An event that starts a workflow or automation
An operation performed in response to a trigger to modify data or advance a workflow
Automatically trigger emails or messages when a respondent completes a survey
Route contacts to different workstreams depending on responses
Send alerts to your team when critical responses are recorded
Obtain API keys from Workflows API and Acumbamail and securely configure them in the connector
Select GET /surveys and GET /surveys/submissions to start syncing data
Run tests verify data integrity and push to production
No extensive coding is needed. The setup uses a no code connector that maps fields between Acumbamail and Workflows API. This makes it accessible to marketers and operations teams. You can start with the two core endpoints to establish a basic sync. As you grow you can add more endpoints and fields.
To start you need the endpoints GET /surveys/ and GET /surveys/submissions. These give you the data you need to create surveys and collect submissions in Workflows. You can later extend with additional endpoints as your workflow requirements expand.
Yes you can customize triggers and actions. The connector supports conditional logic and multiple actions per trigger. You can tailor workflows to send reminders, update records, or route contacts based on survey responses.
Connections use HTTPS and API keys. Treat keys as secrets and rotate them periodically for security. Follow best practices for storing credentials and limit access to the connector.
Yes you can test connections in a staging or sandbox environment before going live. This helps verify mappings and data integrity without impacting production data.
Sync status and logs are visible in the connector dashboard and in Workflows API activity logs. You can review recent runs, failures, and field mappings to diagnose issues.
Yes you can disconnect and reconfigure later. Reauthorizing with new keys or changing endpoint mappings is supported without starting from scratch.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
