Access the Workflows API securely with OAuth 2.0 and/or API keys. Start by creating a client in the API portal, then exchange credentials for access tokens and refresh tokens. Store credentials securely and rotate them on a regular schedule.
Cardly connects to the Workflows API using API tokens tied to your Cardly account. Treat tokens like passwords, keep them secret, and rotate as recommended by your security policy.
Primary endpoints to start with: GET /surveys/ (list surveys) and GET /surveys/submissions (fetch submissions). Additional endpoints (Endpoint3–Endpoint54) are documented in the API docs and can be used as needed.
Trigger: a new survey submission arrives in Cardly.
Actions: retrieve submission details, route to follow-up sequences, and update related records.
GET /surveys/submissions
submission_id, survey_id, responder_email, responses
Trigger: new or updated surveys in Cardly.
Actions: list surveys, fetch details, and sync to analytics or dashboards.
GET /surveys/
survey_id, title, created_at
Trigger: a new submission is received for a tracked survey.
Actions: push data to dashboards, update KPIs, and notify stakeholders.
GET /surveys/submissions
submission_id, survey_id, respondent, responses
Automate data flow between Cardly and your other tools without writing custom code.
Reduce manual tasks, speed up response times, and keep data synchronized across systems.
Scale processes with reliable retries and built-in security features.
Key elements include API endpoints, triggers, actions, and field mappings that connect Cardly with the Workflows API.
A URL path and HTTP method used to request or send data to the Workflows API.
An event-driven mechanism where the Workflows API can push data to Cardly to start a workflow.
A condition that starts a workflow, such as a new submission or survey update.
The process of proving identity and permissions to access the API (tokens, scopes, and secret management).
Use a new submission to trigger onboarding steps, create a contact, and assign tasks in your tools.
Pull survey results into a customer timeline and notify teams of changes.
Stream live survey data to dashboards for up-to-the-minute insights.
Register Cardly as an app in the Workflows API portal and capture client_id and client_secret.
Enter GET /surveys/ and GET /surveys/submissions and set scopes accordingly (surveys.readonly).
Run tests to verify data flow, then switch on live syncing.
No coding is required to connect Cardly with the Workflows API. The integration uses standard API calls and built-in authentication to transmit survey data and submissions. If you are comfortable with API keys and OAuth, you can customize mappings and automate more complex flows.
For a basic sync you only need GET /surveys/ and GET /surveys/submissions to pull surveys and responses. You can extend with additional endpoints later as your automation needs grow.
Test the integration by running a dry run in the Cardly UI, ensuring the correct fields map and that triggers fire. Check logs, confirm data appears in your destination systems, and then enable live mode.
Yes. Use the field mapping controls to specify which Cardly data maps to which Workflows fields. As needed, transform values with simple rules before pushing to endpoints.
The connection uses OAuth tokens or API keys with scoped access and supports TLS encryption. Regular token rotation and best practices ensure security and compliance.
If a submission fails, retry automatically and log the error for troubleshooting. Review the mapping and endpoint health, then re-run the submission or re-trigger the workflow.
See the developer docs for endpoint references, sample payloads, and how-to guides. Join our community or support channels for tailored examples and templates.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
