Use the Workflows API’s secure authentication (OAuth 2.0 or API key) to grant Award Force read-only access to surveys data. The scopes ensure you can pull survey metadata and submissions without modifying records.
Award Force will request permission to read surveys data from the connected Workflows API. Ensure the app is granted the surveys.readonly scope and that credentials are stored securely.
Used endpoints: GET /surveys/ (retrieve surveys) and GET /surveys/submissions (retrieve submissions). Other endpoints can be added as needed (not required for this page).
Trigger: recurring pull of GET /surveys/ and GET /surveys/submissions to keep Award Force records up to date.
Actions: sync surveys to Award Force, attach submissions to the correct survey, update status fields.
GET /surveys/ and GET /surveys/submissions
survey_id, submission_id, status, responder, timestamp
Trigger: a new submission is created at GET /surveys/submissions, enabling immediate workflow execution.
Actions: create or update Award Force records and notify stakeholders, start downstream automations.
GET /surveys/submissions
submission_id, survey_id, author, score
Trigger: on-demand pull of all surveys via GET /surveys/.
Actions: synchronize survey catalog to Award Force and map fields for reporting.
GET /surveys/
survey_id, title, created_at
No-code setup lets you connect Award Force with the Workflows API quickly, without custom development.
Automate data flows, reduce manual data entry, and improve reporting accuracy.
Secure, read-only access ensures data stays protected while enabling powerful automations.
Key elements include endpoints, triggers, actions, data fields, authentication, and mappings. Processes cover setup, testing, monitoring, and auditing your integration.
A standard authorization framework used to obtain access tokens securely.
URLs exposed by the Workflows API to perform actions like fetching surveys or submissions.
A method for real-time data delivery from Workflows API to Award Force when events occur.
The data field correspondences between Workflows API responses and Award Force records.
Use triggers to assign survey responses to the right team in Award Force for faster follow-up.
Schedule survey pulls to align with project calendars and reporting cycles.
Trigger approvals in Award Force as soon as new survey submissions arrive.
Obtain and securely store OAuth tokens or API keys from the Workflows API to authorize Award Force.
Set GET /surveys/ and GET /surveys/submissions and map the response fields to Award Force records.
Run tests, validate data, monitor for errors, and enable production automation.
You can read survey metadata, submissions, and related responses from Award Force using the Workflows API with the surveys.readonly scope. The integration supports pulling data on schedule or via triggers.
No-code connectors enable setup without writing code for standard tasks like authentication, endpoint configuration, and field mapping. For advanced logic, you can layer in external services or custom scripts as needed.
Basic read operations are available via GET /surveys/ and GET /surveys/submissions. More endpoints exist in the Workflows API docs for broader automation.
Credentials should be stored securely using your platform’s secret manager and rotated regularly. Use OAuth tokens with short lifetimes when possible.
Test with sandbox data, verify field mappings, and review logs. Start with a small subset of surveys and submissions before going full production.
Follow the API provider’s rate limits and implement exponential backoff. Cache responses when possible to reduce redundant requests.
Yes. Webhooks and additional endpoints can be integrated to support real-time updates and broader automation scenarios.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
