Skip to main content

Create and triage support tickets with HubSpot, reCAPTCHA and Gmail

Workflow preview

Workflow preview
100%
Create and triage support tickets with HubSpot, reCAPTCHA and Gmail preview
Open on n8n.io

1. Workflow Overview

Quick Overview This webhook based workflow validates form submissions with Google reCAPTCHA, creates or updates a contact in HubSpot, checks for an existing open ticket, and either creates a new Hu...

Best for

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

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.hubspot, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.emailsend, n8n-nodes-base.httprequest, n8n-nodes-base.webhook

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Create and triage support tickets with HubSpot, reCAPTCHA and Gmail
Workflow name
Create and triage support tickets with HubSpot, reCAPTCHA and Gmail

Quick Overview

This webhook-based workflow validates form submissions with Google reCAPTCHA, creates or updates a contact in HubSpot, checks for an existing open ticket, and either creates a new HubSpot ticket or flags it as a duplicate, then emails support and returns an HTML response to the requester.

How it works

  1. Receives a POST request via a webhook containing the customer and complaint details.
  2. Verifies the request using Google reCAPTCHA and stops processing if the verification fails.
  3. Creates or updates the contact in HubSpot and retrieves any tickets associated with that contact.
  4. Looks up the pipeline stage of associated tickets and detects whether an open ticket already exists.
  5. If an open ticket exists, emails the support team with the duplicate details and returns an “already logged” HTML response.
  6. If no open ticket exists, creates a new HubSpot ticket, patches the ticket to set the city property, and returns a “ticket submitted” HTML response.
  7. After returning the webhook response for a new ticket, sends a confirmation email to the customer and a detailed notification email to the support team via Gmail.

Setup

  1. Add a HubSpot App Private Token credential and ensure the configured ticket pipeline ID, stage ID, and ticket owner ID match your HubSpot account.
  2. Replace the reCAPTCHA secret in the Google reCAPTCHA request and ensure your form sends the g-recaptcha-response field to the webhook.
  3. Configure the webhook URL in your form or source system to POST to /hubspot-ticket-webhook with the expected fields (email, first_name, last_name, phone, city, remarks, order_no).
  4. Set up Gmail credentials for the customer and CS team emails, and update sender/recipient addresses (for example, [email protected] and [email protected]).
  5. Update placeholder values in the HTML/email content (YOUR_HUBSPOT_PORTAL_ID, example.com tracking URL, and YOUR_SUPPORT_PHONE) to match your environment.

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 - Sticky Note4

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

Block 6 - Sticky Note5

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

Block 7 - Sticky Note6

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

Block 8 - Sticky Note7

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

Block 9 - Create or update a contact1

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

Block 10 - Data Sorting1

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

Block 11 - Code in JavaScript2

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 12 - If1

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

Block 13 - Create a ticket1

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

Block 14 - Code in JavaScript3

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 15 - Send email1

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 16 - Find Ticket Status1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 17 - Find if Ticket Exit1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 18 - Webhook

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2.1

Block 19 - Respond to Webhook

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1.4

Block 20 - Code in JavaScript4

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 21 - Respond to Webhook1

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1.4

Block 22 - Code in JavaScript5

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 23 - HTTP Request1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Block 24 - Google-captcha

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.3

Showing the first 24 of 28 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Create and triage support tickets with HubSpot, reCAPTCHA and Gmail
Complexity advanced
Nodes 28
Categories Ticket Management
Author Shahzaib Anwar
Published 15 Jun 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/16368/16368.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 and triage support tickets with HubSpot, reCAPTCHA and Gmail do?

Quick Overview This webhook based workflow validates form submissions with Google reCAPTCHA, creates or updates a contact in HubSpot, checks for an existing open ticket, and either creates a new Hu...

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.