> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations.md).

# HubSpot Integration in Automations

Connect HubSpot tickets, contacts, companies, deals and conversations to Ebbot Automations. The **HubSpot Workflow Server** provides the triggers and actions used by your workflows; prompts, conditions and knowledge retrieval are configured in Automations.

Use this guide to connect the integration, inspect the exact input/output fields, and build workflows that read records, prepare internal notes, send replies or update ticket properties.

## Start here

1. [Connect HubSpot](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/connection-setup.md): credentials, permissions and a first read-only test.
2. [Incoming HubSpot Ticket Webhook](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/incoming-hubspot-ticket-webhook.md): register ticket events, understand output fields and filter unwanted updates.
3. [Action reference](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/actions.md): all 25 documented actions, with required fields, defaults, output paths and behavior.
4. [Workflow patterns](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/workflow-patterns.md): new-ticket triage, internal assistance and reply follow-up.
5. [Troubleshooting](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/troubleshooting.md): missing events, permissions, incomplete transcripts, pagination and send outcomes.
6. [Incoming Button Click](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/incoming-button-click.md): an alternative trigger for signed resolution links, used with Generate Resolution Buttons.

## How a ticket event becomes an action

Example: you build a workflow that adds an internal note when a new ticket arrives.

```mermaid
flowchart TD
    A["1. HubSpot: a ticket is created"] -->|"Webhook"| B["2. Workflow Server: the ticket trigger receives the event"]
    B -->|"Start the workflow"| C["3. Automations: check conditions, read the ticket and prepare a note"]
    C -->|"Run Add Internal Ticket Note"| D["4. Workflow Server: send the note to HubSpot"]
    D --> E["5. HubSpot: the internal note appears on the ticket"]
```

**HubSpot** sends the event and stores the resulting note. **Automations** runs the workflow you build and decides what should happen. The **HubSpot Workflow Server** provides both the trigger that receives the event and the actions that read or write HubSpot data.

Step 3 is configured in your workflow: you choose its conditions, actions and any LLM or knowledge-retrieval nodes. This example is not created automatically when you connect HubSpot.

A **connection** stores the credentials and API URL. An **installed trigger subscription** connects incoming events to a workflow through its own callback URL. You must also configure the event subscriptions and target URL in the HubSpot app.

The integration exposes two triggers: `incoming_hubspot_ticket_webhook` and `incoming_button_click`. There is no general Create Ticket action in this catalog. A chat Extension or another system that creates tickets is a separate component, even when its data is later read by these workflows.

## Choose the right output

* `Get Ticket` returns `ticket.properties` and `ticket.full_conversation_content`.
* `Get Contact from Ticket` returns a contact **ID**; follow it with `Get Contact` for contact properties.
* CRM schema actions describe fields and allowed values; they do not read those values from a specific record.
* Internal comments and CRM Notes are different objects. Choose the correct inclusion option when reading them.
* `success: true` describes an action's result. In particular, the public-comment fallback can log an email without delivering it. See [Add Public Ticket Comment](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/actions/add-public-ticket-comment.md).

Select variables from the node output picker instead of typing an assumed placeholder path. For structured classification, use the separate Automations [LLM node contract](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/workflow-nodes/llm-nodes): the LLM's `.structuredOutput` is distinct from this connector's CRM outputs.

## For agents helping with a customer solution

Read the relevant action or trigger page before changing a node. Then inspect the customer's current published flow and a real run. Resolve their queue values, owners, pipelines and business rules from that customer's configuration; none are universal defaults of this integration.

For updates, check which events your own writes generate. Use explicit conditions before classification and side effects. Verify the destination record or message after a test, and preserve the prior flow version so changes can be reversed.

## Reference scope

Reviewed against the HubSpot Workflow Server implementation on **29 September 2026**. This reference describes connector contracts and implementation limits; it is not an audit of your portal or a guarantee that a particular deployment already exposes every documented action. If a field or action is unavailable in your installed integration, ask Ebbot to confirm its version before redesigning the flow around an assumed output.

General product guidance: [Understanding Workflows](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/understanding-workflows), [Condition Nodes](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/workflow-nodes/condition-nodes) and [Dashboard and Monitoring](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/dashboard-and-monitoring).