Use the provided OAuth 2.0 flow or API key mechanism to grant Radius CRM access to Workflows API with the surveys.readonly scope.
Authorize Radius CRM to connect to Workflows API and select the needed permissions to read survey data.
Primary endpoints: GET /surveys/ and GET /surveys/submissions; additional endpoints may be enabled as needed for extended data flows.
Trigger when new surveys are created in Workflows API to pull survey metadata into Radius CRM.
Actions include mapping survey fields to Radius CRM records and storing response counts.
GET /surveys/
survey_id, title, status, created_at
Trigger on new submissions in Radius CRM to send to Workflows API.
Actions include creating submissions, attaching responses, and updating status.
POST /surveys/submissions
survey_id, user_id, responses, timestamp
Trigger on submission status updates to reflect in Radius CRM.
PATCH /surveys/submissions/{id}
submission_id, status, last_updated
Build powerful automations without writing any code.
Eliminate manual data entry and reduce errors through structured field mappings.
Gain real-time visibility with live data syncing and dashboards.
Understand endpoints, triggers, actions, and field mappings that move data between Workflows API and Radius CRM.
An Application Programming Interface that lets apps communicate and exchange data.
A specific URL with an HTTP method used to perform a defined action in an API.
A real-time notification sent from one app to another when an event occurs.
The process of proving identity to gain access to an API, typically via OAuth or API keys.
Map respondent data to contact records and keep notes with survey metadata for context.
Attach survey title, date, and results as activities in Radius CRM for quick reference.
Visualize live submission counts and statuses to monitor engagement at a glance.
Grant Radius CRM access to Workflows API and select surveys.readonly scope for read access.
Map survey_id, title, and responses to corresponding Radius CRM fields and set triggers.
Run a test submission, verify data flow, and enable the integration for ongoing use.
No coding is required. Use the visual mapping and built‑in triggers to connect Workflows API with Radius CRM. Leverage templates to speed setup. If you prefer, our support team can help you tailor mappings to your data model. You’ll configure authentication, select the surveys.readonly scope, and test with a sample submission before going live.
Core endpoints used are GET /surveys/ to list surveys and GET /surveys/submissions to fetch responses. Additional endpoints may be enabled if you extend data flows, but the essential read path for Radius CRM is covered by these two.
Security uses OAuth 2.0 or API keys with API‑level access control. Radius CRM should restrict access to permitted IPs and monitor activity through audit logs. Always keep credentials confidential and rotate keys as recommended.
Yes. You can map multiple fields from surveys and submissions to corresponding fields in Radius CRM, including custom fields and notes. Use the mapping interface to align data types and formats.
If a submission fails, check the error message from Workflows API, review field mappings, and verify permissions. Re-run the failed submission after correcting any issues and enable retry logic where appropriate.
Yes. The integration supports read-only access, allowing you to pull survey data into Radius CRM for reporting and analysis without modifying data on Workflows API.
Rate limits are defined in the Workflows API docs. If you hit limits, stagger requests, batch submissions, or contact support for higher quotas during critical campaigns.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
