Tby Typeform
Send responses to a webhook
Creates or updates a named webhook that posts each new response to a form to your URL.
Description
Name the webhook with `tag`, set `url` and `enabled: true`, and pass a `secret` so each payload is signed with HMAC SHA-256 and can be verified. Use `event_types`, such as `form_response_partial`, to choose the events it receives. The MCP server doesn't manage form-level webhooks; over MCP, add a webhook step to an automation with `automations-public_add_webhook_step`.
create-webhook.md
Send responses to a webhook
Creates or updates a named webhook that posts each new response to a form to your URL.
Name the webhook with tag, set url and enabled: true, and pass a
secret so each payload is signed with HMAC SHA-256 and can be verified.
Use event_types, such as form_response_partial, to choose the events it
receives. The MCP server doesn't manage form-level webhooks; over MCP, add a
webhook step to an automation with automations-public_add_webhook_step.
Set up
Use the first option your agent supports.
API (official)
- Base URL: https://api.typeform.com
- Endpoint:
PUT /forms/{form_id}/webhooks/{tag} - Auth: send the header
Authorization: Bearer $TYPEFORM_API_KEY - Get a key: https://admin.typeform.com/user/tokens
- Docs: https://www.typeform.com/developers/get-started/
Before doing anything else, make one read-only call to confirm access.
Rules
- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
Built from these files in the repository
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.
Ways in
| Route | Source | Call | Required | Docs |
|---|---|---|---|---|
| Official | PUT /forms/{form_id}/webhooks/{tag} | API key in $TYPEFORM_API_KEY | Docs |