Ticketing
Ticketing
Section titled “Ticketing”FormFlow can automatically create a ticket, issue, or conversation in your support or project management tool whenever a customer submits a form. Multiple ticketing providers can be connected simultaneously.
Setting Up a Ticketing Provider
Section titled “Setting Up a Ticketing Provider”- Go to Settings and open the Ticketing tab
- Find the provider you want to connect and enter your credentials
- Click Test Connection to verify
- Click Save
Once connected globally, enable ticket creation for a specific form in that form’s Integrations tab, where you also configure field mappings and provider-specific options (such as which project or queue to create the ticket in).
Supported Providers
Section titled “Supported Providers”Creates Jira issues (Software or Service Management).
| Field | Description |
|---|---|
| Site URL | Your Atlassian site URL, e.g. https://yourorg.atlassian.net |
| Account Email | The email address associated with your Atlassian account |
| API Token | Generate at id.atlassian.com → Security → API tokens |
Per-form configuration (in the form’s Integrations tab): project key, issue type, field mappings.
Zendesk
Section titled “Zendesk”Creates Zendesk support tickets.
| Field | Description |
|---|---|
| Subdomain | Your Zendesk subdomain, e.g. yourorg for yourorg.zendesk.com |
| Agent Email | Email address of a Zendesk agent |
| API Token | Generate in Zendesk: Admin → Apps and Integrations → Zendesk API |
Freshdesk
Section titled “Freshdesk”Creates Freshdesk tickets.
| Field | Description |
|---|---|
| Subdomain | Your Freshdesk subdomain, e.g. yourorg for yourorg.freshdesk.com |
| API Key | Find in Freshdesk: click your avatar → Profile Settings → API Key |
HubSpot Service Hub
Section titled “HubSpot Service Hub”Creates HubSpot tickets.
| Field | Description |
|---|---|
| Access Token | A HubSpot Private App access token with crm.objects.tickets.write, crm.objects.tickets.read, and files scopes |
Per-form configuration (in the form’s Integrations tab): pipeline ID, pipeline stage ID, field mappings. Find pipeline and stage IDs in HubSpot under Service → Pipelines.
Intercom
Section titled “Intercom”Creates conversations in Intercom. If the customer’s email doesn’t exist in Intercom, a new contact is created automatically.
| Field | Description |
|---|---|
| Access Token | An Intercom access token from your Developer Hub → Your App → Authentication |
Per-form configuration (in the form’s Integrations tab): field mappings. Mapping a field to the contact email is required.
Linear
Section titled “Linear”Creates issues in Linear.
| Field | Description |
|---|---|
| Personal API Key | Generate in Linear: Settings → API → Personal API keys |
Per-form configuration (in the form’s Integrations tab): team ID, label IDs, state IDs, field mappings. Find these IDs in Linear under Settings → Teams and Settings → Labels.
ServiceNow
Section titled “ServiceNow”Creates records in ServiceNow (incidents, cases, or custom tables).
| Field | Description |
|---|---|
| Instance URL | Your ServiceNow instance URL, e.g. https://yourorg.service-now.com |
| Client ID | OAuth application client ID — create an OAuth Application Registry entry in ServiceNow first |
| Client Secret | OAuth application client secret |
Per-form configuration (in the form’s Integrations tab): target table, field mappings.
Generic Webhook
Section titled “Generic Webhook”Sends form submissions as a JSON POST request to any HTTPS endpoint. Use this to connect FormFlow to any service not natively supported.
| Field | Description |
|---|---|
| Webhook URL | Your endpoint URL (must use HTTPS) |
| Auth Token | Optional — sent as a Bearer token in the Authorization header |
| Custom Header Name | Optional — a custom HTTP header name to include |
| Custom Header Value | Optional — the value for the custom header |
The JSON payload includes all submitted field values plus a _meta envelope containing the form ID, submission ID, and submission timestamp.
Click Send Test Payload to verify your endpoint receives the request correctly.