Crmble authenticates to the Workflows API using either an API key or OAuth 2.0. Choose the method that fits your project and enter the credentials in Crmble’s connection settings.
To authorize Crmble with the Workflows API, create credentials in the API, then paste the token or client credentials into Crmble’s connection screen. Save and test the connection.
Endpoints in this guide include GET /surveys/ to list surveys and GET /surveys/submissions to fetch submissions. Additional endpoints are available in the API reference as your integration grows.
Trigger: Crmble sends authenticated requests to Workflows API when a survey is created or a submission is updated.
Actions: Retrieve surveys, pull submissions, and push results using standard GET calls.
GET /surveys/; GET /surveys/submissions
survey_id, submission_id, timestamp
Trigger: You authorize Crmble to access your Workflows API account.
Actions: Obtain access token and refresh token; use token to call endpoints.
GET /surveys/; GET /surveys/submissions
client_id, client_secret, access_token
Trigger: Crmble events push data to Workflows API via webhooks.
Actions: Create or update Workflows API resources when Crmble detects changes.
Depends on the endpoint; typically POST/PUT for updates, GET for reads.
webhook_id, payload_signature
No-code automation: set up connections in minutes without writing code.
Real-time data sync between Crmble and Workflows API to keep dashboards current.
Centralized workflow automation across apps and surveys.
Below are essential terms and process steps to help you understand the Crmble ↔ Workflows API integration.
A secret token used to authenticate API requests.
A URL path in the API that performs a specific action.
An authorization framework that grants limited access to an API on behalf of a user.
A method for apps to send real-time data to each other via HTTP callbacks.
Automatically generate surveys in Workflows API when a Crmble submission is received.
Push changes in Crmble contacts to the corresponding records in Workflows API.
Keep Crmble and Workflows API statuses aligned for accurate reporting.
In Workflows API, generate an API key or OAuth client credentials for Crmble.
Enter your credentials into Crmble’s connection setup and select the required permissions.
Run test calls, verify data flow, and enable the integration for production.
You can authenticate Crmble to Workflows API using an API key or OAuth 2.0. Start by generating an API key in the Workflows API console and selecting Crmble as a trusted app. In Crmble, paste the key into the authentication field and save. Test the connection to confirm access to GET /surveys/ and GET /surveys/submissions. If you prefer OAuth, register Crmble as an OAuth client, obtain an authorization code, exchange it for an access token, and refresh tokens as needed. Crmble will use this token to sign requests automatically.
Crmble will utilize the endpoints relevant to surveys and submissions: GET /surveys/ to list surveys and GET /surveys/submissions to retrieve submissions. Other endpoints may be used as you extend the workflow, such as creating or updating submissions or surveys. Refer to the API reference for endpoint details and required parameters. You can test calls directly from Crmble’s connection tester or from your API client to verify responses before going live.
Yes. No-code automation allows you to set up a Crmble ↔ Workflows API connection without writing code. Use Crmble’s built-in connectors to map data fields and trigger actions based on survey events. For advanced users, you can still customize endpoints, triggers, and data mappings via the API reference and conditional logic in Crmble’s automation builder.
Absolutely. The no-code setup guides you through credentials, endpoint selection, and mapping fields. You can test the integration and enable it with a single click. If needed, Crmble offers a guided setup flow to simplify common use cases.
Credentials may expire or be rotated periodically. If a token becomes invalid, Crmble will prompt you to re-authenticate or refresh the token. In API-key scenarios, rotate keys regularly and revoke unused keys.
Common issues include invalid credentials, insufficient scopes, or network errors. Start by re-checking your Crmble connection settings, verifying the credentials, and ensuring the Workflows API is reachable. Review error messages and consult the API reference for required parameters.
API documentation is available in the Workflows API reference and Crmble integration guides. You can access the docs from Crmble’s connector page or the Workflows API developer portal. If you need help, contact support with your account details.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
