> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Use HubSpot in Deepline

> Use list/get/search for flexible CRM reads, batch operations for large syncs, marketing campaign and email tools for outbound orchestration, sequence tools for.

[Human guide: work with your agent →](https://deepline.com/docs/human/providers/hubspot/guide.md)
Inspect one HubSpot action before starting provider-backed work. Your first result is a verified input and output contract.

## Provider-specific requirements

### Quick Reference

| Goal | Operation | Notes |
| - | - | - |
| Create a company | `hubspot_create_company` | Use `website_url` when you want HubSpot to infer the domain. |
| Create a contact | `hubspot_create_contact` | Prefer `email` for stable identity matching. |
| Create a deal | `hubspot_create_deal` | Use `deal_stage` and `deal_probability` only when you know the pipeline. |
| Create a ticket | `hubspot_create_ticket` | Use `hubspot_list_ticket_pipelines` first when you do not know stage IDs. |
| Create a note | `hubspot_create_note` | `time_stamp` is required. Add associations to place it on a record timeline. |
| Create a task | `hubspot_create_task` | `task_type` should usually be `TODO`. |
| Update a record | `hubspot_update_*` | Always include `id` and only the fields you want to change. |
| Delete a record | `hubspot_delete_*` | Hard delete only when the target should disappear from HubSpot. |
| Browse records | `hubspot_list_*` | Use for paging and record inspection. |
| Fetch one record | `hubspot_get_object` | Best when you already have the record ID. |
| Search records | `hubspot_search_objects` | Best for fuzzy lookups and filters. |

### Practical Notes

* HubSpot normalizes most writes to CRM property names such as `firstname`, `lastname`, `hubspot_owner_id`, and `dealstage`.
* For object-heavy workflows, prefer `search_objects` over broad listing when you need filters or quick lookup by email/domain.
* The `list_objects` and `get_object` helpers work for standard objects and custom objects when you know the object type.
* When using notes or tasks, add associations up front so the activity lands on the right record timeline.
* For support workflows, prefer ticket-specific tools. Use `hubspot_search_tickets` or `hubspot_list_tickets` for deduplication and SLA sweeps. Use batch ticket tools for backfills and sync repairs. Use `hubspot_transition_ticket_stage` for status changes. Use `hubspot_associate_ticket` or `hubspot_remove_ticket_association` for contact, company, or GitHub-sync links. Use `hubspot_add_ticket_note` or `hubspot_pin_ticket_activity` for timeline updates.

## Find an applicable action

Confirm your effective workspace, then search the live catalog:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
deepline search "HubSpot" --type tools --json
```

Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

## Inspect the selected contract

Replace `<returned-tool-id>` with the identifier returned by discovery:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe <returned-tool-id> --json
```

These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits.

A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

## Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept.

Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects.

For reusable logic, follow [Write Plays](https://deepline.com/docs/sdk-v2/plays.md). For direct-call recovery, use [Tool execution recovery](https://deepline.com/docs/sdk-v2/tool-execution-recovery.md).

> [!TIP]
>
> Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.