Skip to main content

Create HubSpot support tickets from Tally form submissions

Workflow preview

Workflow preview
100%
Create HubSpot support tickets from Tally form submissions preview
Open on n8n.io

1. Workflow Overview

️ Self hosted only — This template uses a community node ( ) and cannot run on n8n Cloud. Who it's for This workflow is for support, operations, or customer success teams that use Tally for i...

Best for

  • Ticket Management automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-tallyforms.tallytrigger, n8n-nodes-base.hubspot, n8n-nodes-base.if, n8n-nodes-base.set

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Growth AI.

Original n8n.io source

1.1 Workflow description

Title
Create HubSpot support tickets from Tally form submissions
Workflow name
Create HubSpot support tickets from Tally form submissions

> ⚠️ Self-hosted only — This template uses a community node (n8n-nodes-tallyforms) and cannot run on n8n Cloud.

Who it's for

This workflow is for support, operations, or customer success teams that use Tally for intake forms and HubSpot as their CRM. It automates ticket creation so no submission is lost and every ticket is linked to the right contact.

How it works

  1. A Tally form submission triggers the workflow via webhook.
  2. HubSpot is searched for an existing contact matching the submitted email address.
  3. An If condition checks whether a matching contact was found.
  4. If no contact exists, a new HubSpot contact is created or updated with the submitted details.
  5. Contact ID, first name, and last name are normalized from whichever branch was taken.
  6. A new HubSpot support ticket is created and associated with the resolved contact.

How to set up

  • Install the n8n-nodes-tallyforms community node on your self-hosted n8n instance.
  • Connect your Tally account and set the correct form ID in the Tally trigger node.
  • Connect your HubSpot account (app token or OAuth) to the Search, Upsert, and Create Ticket nodes.
  • Map Tally form fields (email, first name, last name) to HubSpot contact properties in the Upsert node.
  • Configure ticket properties (pipeline, stage, subject) in the Create HubSpot Ticket node to match your HubSpot setup.

Requirements

  • Self-hosted n8n instance
  • n8n-nodes-tallyforms community node
  • Tally account with a published form
  • HubSpot account with API access (app token or OAuth)

How to customize

  • Extend the Set node to pass additional Tally fields (e.g., message body, phone number) into the ticket description or custom properties.
  • Add a follow-up step after ticket creation to send a confirmation email to the submitter via Gmail or SendGrid.
  • Replace the Tally trigger with another form tool (e.g., Typeform or Jotform) by swapping the trigger node and remapping the field references.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - When Tally Form Submitted

Type / Role
n8n-nodes-tallyforms.tallyTrigger - tallyTrigger
Config choices
Version 2

Block 6 - Search HubSpot Contacts

Type / Role
n8n-nodes-base.hubspot - hubspot
Config choices
Version 2.2

Block 7 - Create HubSpot Ticket

Type / Role
n8n-nodes-base.hubspot - hubspot
Config choices
Version 2.2

Block 8 - Upsert HubSpot Contact

Type / Role
n8n-nodes-base.hubspot - hubspot
Config choices
Version 2.2

Block 9 - If Contact Already Exists

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 10 - Set Contact ID and Name

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

3. Summary Table

Workflow Create HubSpot support tickets from Tally form submissions
Complexity intermediate
Nodes 10
Categories Ticket Management
Author Growth AI
Published 30 Mar 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/14474/14474.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Create HubSpot support tickets from Tally form submissions do?

️ Self hosted only — This template uses a community node ( ) and cannot run on n8n Cloud. Who it's for This workflow is for support, operations, or customer success teams that use Tally for i...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management use case.