Access to the Workflows API is secured with an API key or OAuth token. Use your key in the Authorization header (Bearer
Establish a trusted link from Act! to the Workflows API by configuring a service account or OAuth credentials in Act!, and storing them securely in your connector settings.
Primary endpoints used: GET /surveys/ and GET /surveys/submissions. Additional endpoints are available in the API docs but not shown here.
Trigger: New or updated survey in Workflows API
Actions: Use GET /surveys/ to fetch surveys, then GET /surveys/submissions to pull related submissions and sync them to Act!
GET /surveys/
survey_id, title, created_at
Trigger: New submission received for a survey
Actions: Call GET /surveys/submissions to retrieve the new submission and write it into Act!
GET /surveys/submissions
submission_id, survey_id, responder_email, submitted_at
Trigger: Manual or scheduled export
Actions: Retrieve both surveys and submissions (GET /surveys/, GET /surveys/submissions) and export to Act!
GET /surveys/ and GET /surveys/submissions
survey_id, submission_id, title, submitted_at
Build automations without writing code—drag, drop, and connect to sync surveys and submissions into Act! CRM.
Centralized data flow reduces manual data entry and improves response follow-ups in Act!.
Scalable, auditable workflows with repeatable processes across teams.
This glossary covers the core concepts used in connecting the Workflows API to Act! including endpoints, triggers, actions, and data fields.
A programmable interface that lets apps communicate and share data securely over HTTP.
A specific path on an API that performs a function or returns data, e.g., /surveys/.
A callback URL that gets invoked when a particular event occurs, enabling real-time data sync.
A standard authorization framework that enables secure access without exposing user credentials.
When a survey is submitted, automatically create or update a contact or lead in Act! with key details from the response.
Stream live survey results into Act! so teams can monitor responses and act quickly.
Schedule regular exports of surveys and submissions to keep Act! CRM up to date.
In the Workflows API connector, provide Act! credentials or OAuth app details to establish a trusted link.
Select GET /surveys/ and GET /surveys/submissions and map fields like survey_id, title, and submission data to Act! fields.
Run a test to verify data flow, then save the configuration and enable automatic syncing.
Use API keys or OAuth tokens to authenticate to the Workflows API. Include the token in the Authorization header (Bearer
The primary endpoints are GET /surveys/ and GET /surveys/submissions. Other endpoints exist in the API documentation but are not shown here. You can test endpoints with your connector’s built-in test tool. Consult the API docs for field schemas and example requests to help with mapping and validation.
Map survey fields to Act! fields such as survey_id -> Survey ID and title -> Survey Title. For submissions, map submission_id, responder_email, and submitted_at to corresponding Act! records. Use transformation steps if needed to format dates or combine fields for a clean Act! record.
No coding is required. Use the Workflows API connector with Act! in a no-code environment like Zapier or a dedicated connector. You can add simple conditionals and data transforms, but complex logic is optional for most use cases.
Data synced includes survey_id, title, created_at, submission_id, responder_email, and submitted_at. You can choose to sync these automatically into Act! records such as Contacts, Leads, or Tasks depending on your field mappings. This helps maintain up-to-date records and enables targeted follow-ups.
Rate limits depend on your Workflows API plan. If polling, stagger requests and cache results to minimize calls. For near real-time updates, consider webhooks where supported, and implement robust error handling and retries.
Endpoint details and examples are available in the Workflows API documentation. Look for sections covering /surveys/ and /surveys/submissions. Use your connector test tool to try sample requests and verify field mappings and response schemas.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
