Configure an integration

This is the common procedure for a form integration. The exact screens and fields differ by provider.

Example: send test results to an approved destination

1. In the test form, create a simple non-sensitive test submission that includes only the fields you need to map.
2. Select Integrations and choose the destination, for example Google Sheets, Slack, or WebHooks.
3. Authenticate to the destination only with the authorized organization account. Read the consent/permissions prompt before approving access.
4. Choose the destination resource, such as the spreadsheet, channel, folder, list, board, project, or webhook endpoint.
5. Map each destination value to the exact form field. Confirm names rather than relying on field order.
6. Save and run a test submission.
7. Inspect the destination. Verify data values, file handling, duplicates, date/time format, and who can view the destination.
8. Record the integration owner, destination, mapped fields, error owner, and offboarding/revocation process.

Expected result

Only the approved form data arrives at the intended destination in an understandable format. A failed destination does not silently cause a critical business process to be missed.

Webhooks and custom endpoints

For WebHooks, use an HTTPS endpoint controlled by the organization. Treat payloads as potentially sensitive, authenticate the receiver, validate incoming data, and test response/error handling. Never put a secret token into an ordinary field, hidden field, or client-visible Code field.