Authenticate requests to the Workflows API using API keys or OAuth2 tokens. Store credentials securely and rotate secrets regularly.
Configure KrispCall to authorize with the Workflows API using the supported method (API key or OAuth2) and manage tokens with least-privilege access.
– GET /surveys/ — Retrieve all surveys – GET /surveys/submissions — Retrieve submissions for a selected survey Note: Additional endpoints can be enabled as your workflows grow.
Trigger on a new or updated survey to initiate KrispCall automation.
Actions: retrieve surveys, then fetch associated submissions, and start KrispCall call sequences.
GET /surveys/
id, title, created_at
Trigger on new survey submissions to trigger KrispCall actions.
Actions: fetch submissions, map to leads, fire KrispCall steps.
GET /surveys/submissions
survey_id, submission_id, respondent_email
Trigger: manual or scheduled pull to sync all surveys.
Actions: list all surveys, generate summaries, and export data to KrispCall for reporting.
GET /surveys
id, title, status
Rapid automations: build triggers and actions without writing code.
Centralized data: access survey insights directly in KrispCall dashboards.
Scalability: easily add new endpoints and expand workflows over time.
Key elements include endpoints, triggers, actions, and mappings that connect KrispCall to the Workflows API.
A URL path in the API used to retrieve or modify data, e.g., GET /surveys/.
The method used to verify identity and authorize requests (API keys, OAuth2 tokens).
An event that starts an automation, such as a new survey submission.
An operation performed as part of an automation, such as fetching data or creating a record.
Send instant KrispCall call prompts whenever a survey submission occurs to accelerate follow-ups.
Leverage survey responses to segment leads and tailor KrispCall outreach.
Aggregate API data to power KPI dashboards in KrispCall.
Obtain your API key or OAuth credentials from the Workflows API console and store them securely.
Map the available endpoints to KrispCall workflows and set appropriate triggers.
Run tests, verify data flow, and set up alerts for failures and retries.
We support API key-based authentication and OAuth2 tokens. Choose the method that fits your security requirements. Rotate credentials regularly and use least-privilege scopes to limit access.
The core endpoints shown include GET /surveys/ and GET /surveys/submissions. Additional endpoints can be enabled as your use case grows. Refer to the API docs for a full list and usage examples.
You can set a trigger to fire when a survey is submitted, then call KrispCall actions to initiate calls or notifications. In your automation builder, map the submission data to KrispCall fields to personalize outreach.
No traditional code is required for the basic integration; it can be built with no-code automation tools. If you need custom logic, you can add small scripts or Webhooks, but typical tasks are done with endpoints, triggers, and actions.
You can access survey details, submissions, respondent contact data, and related metadata depending on your permissions. Respect privacy and data handling requirements when exporting or storing data.
Use sandbox or test endpoints, run end-to-end tests, and monitor logs in your automation tool. Set up alerts for failures and validation checks to ensure data integrity.
Yes. You can add additional endpoints later by updating the integration configuration and refreshing mappings. As your needs grow, extend triggers, actions, and field mappings to cover new workflows.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
