Skip to content
Docs menu

Send form responses to Notes, Tasks, Funnel, Support, Calendar, webhooks and Slack

Connect a form to seven destinations, from a Notes database row to a Funnel deal or a booking link. Deliveries run after the response is saved, retry on failure and keep a log.

View .md

The Connect tab (/forms/{id}?tab=connect) sends each response where your team already works. Responses are kept in Venom Forms whatever you connect. A destination never slows the respondent down: submitting writes the response and one queue entry per destination in a single transaction, and the sweep delivers from the queue within a minute.

Destination (kind) What a response becomes
Notes database (globe) A row in a database in the org vault, as the system actor "Venom Forms" (so versions, links and the audit log apply).
Tasks triage (tasks) An issue in the chosen team's Triage; the title comes from a template and the answers are the description.
Webhook (webhook) A signed forms.response.created event to every org webhook endpoint that takes it.
Slack (slack) A message in a channel, through your org's own Slack app.
Funnel deal (funnel_deal) A person in People (made or matched from the contact answers) and a deal for them in a Funnel pipeline.
Support conversation (support_conversation) A conversation in the Support inbox, with the answers as its first message.
Book a meeting (calendar_booking) A routing form: the respondent books the Venom Calendar event type their answers point to, right after they submit.

Every response goes to the destinations that are switched on, however it came in: from the form's page, or from a backend through POST /forms/api/v1/forms/{id}/responses or forms_response_create (server-to-server submits).

Notes database

Pick an existing database in the org vault, or Create a database for these responses: it gets a property per question and a Submitted time. The tab proposes a mapping and lets you change it per question.

Question Property
the first short text title (the row's name)
other short and long text, ranking, hidden field text
email, phone, website email, phone, URL
number, rating, opinion scale, NPS number
multiple choice, dropdown select (options by label; new ones are added)
checkboxes multi-select
yes/no checkbox
date date
file upload files (links to the files; opening them needs permission to read the form's responses)

Without a title question the row is named after the form and the time.

Tasks triage

Choose a team that has Triage on. The issue title is a template: Lead {{block:<question id>}} ({{block:<plan id>}}) (choices appear by label). The description lists every answered question, with file links. Tasks' AI triage then runs as it does for any triage issue: it only suggests, unless the team turned automatic triage on.

Webhook

Add an endpoint under Settings → Webhooks and tick Form response, or use an existing one. The body has the form's id and title, the response id, the version and the time, and a link. It carries the answers only when the form's Include the answers switch is on, since answers can be personal data. The event is signed and retried like every org webhook.

Slack

Add your org's Slack app (Integrations) with its bot token, invite the app to the channel, and enter the channel. The message names the form and links to the responses; the answers are in it only when Include the answers is on.

Funnel deal

A person in People and a deal in a Funnel pipeline for every response. Pick the pipeline, the stage (default: its first open stage), the owner (the member who gets the new person and the deal; People is personal, so they must belong to someone), and which question holds the contact's name (required), email, phone, company, role, LinkedIn and the deal value. The deal title is a template ({{name}} or {{block:<id>}}; default Form title: name).

The contact goes through the same matching as capture: a person the owner already knows with the same email, phone, Telegram, LinkedIn, X or website is reused (their new facts added, the form logged as an interaction); otherwise a new private person is made. The deal is linked to them and carries form:<form>:<response> as its source, so a retry after a crash opens nothing twice. A response with no name is skipped; an owner who left the org fails the delivery with that reason until you choose another. A value that is not a plain amount (3k) leaves the deal's value empty rather than guessing. Agents add it with forms_form_connect (kind: "funnel_deal", config {pipeline, stage?, owner, map: {name, email?, ...}, title?, currency?}).

Support conversation

A conversation in the shared Venom Support inbox for every response. Choose the question that holds the customer's email (replies go there) and, optionally, their name and company, a priority, and a subject template ({{name}} or {{block:<id>}}; default Form title: name). Every answer becomes the conversation's first message, with uploaded files as links. The conversation carries form:<form>:<response> as its source, so a retry after a crash opens nothing twice. A response with neither a valid email nor a name is skipped. Replies go out only through the email provider you connect in Support settings (Support email). Agents add it with forms_form_connect (kind: "support_conversation", config {map: {email?, name?, company?}, subject?, priority?, tags?}).

Book a meeting

A routing form for Venom Calendar. Its rules read the answers with the same conditions as the form's own logic (if Company size > 50 …), first match wins, and each points to an event type of this org that is switched on (optionally one host of a round-robin one) or to a URL. A fallback covers answers no rule matches. Choose the question that holds the respondent's email (required) and, optionally, their name.

Unlike the other destinations this one acts on the submit itself: the respondent's next step is a single-use booking link (/meet/l/…, valid 14 days, prefilled with their name and email), shown inline on the form, or the rule's URL they are sent to. The booking follows the event type's own rules, as on its public page. When nothing matches, or the event type is gone or switched off, the form's own thank-you shows instead. The queued delivery then only records where the response went (the event type and host, the URL, or why it was skipped). A server-to-server submit gets the same link in its answer (booking, redirect) to pass on. Agents add it with forms_form_connect (kind: "calendar_booking", config {rules: [{when: {mode, conditions}, then: {event_type_id, host?} | {url}}], fallback?, map: {email, name?}}).

Deliveries

Each delivery is tried at once, then again after 1 minute, 5 minutes, 30 minutes and 2 hours; after the fifth failure it is marked failed. The Delivery log shows state, attempts, the last error and what was made (the issue's identifier, the row's note id). The log never holds an answer. Retry sends a failed one again. Delivery is at least once and one per response and destination: the webhook event has the response id as its dedupe key, and the queue entry is unique, so a response is never queued twice. If a worker dies in the instant between making a row and recording it, that one row, issue or message can repeat.

A destination removed or switched off before its turn is skipped. Deleting a form removes its queue.

For agents

forms_form_connect lists, adds and removes destinations and retries deliveries. Add a Notes destination with config: {databaseId} (questions are matched to properties by name) or config: {createDatabase: true}; a Tasks one with {team: "ENG", title: "…"}; Slack with {channel: "#leads"}; Funnel, Support and Book a meeting with the configs in their sections above. Set includeAnswers with forms_form_update (setSettings). REST: GET /forms/api/v1/forms/{id}/deliveries, POST …/deliveries/{deliveryId}/retry, GET /forms/api/v1/connect (what can be chosen).