Connect Box to HubSpot

Creates a signature request. This involves preparing a document for signing and sending the signature request to signers. See the documentation.

Downloads a file from Box to your workflow's /tmp directory. See the documentation

Fetches comments for a file. See the documentation.

Extracts text from a file in Box. See the documentation

Lists files, folders, and web links in a Box folder. Use 0 for the root folder. Returns one page of results (default 100, max 1000). To find items by name or metadata across all folders, use **Search Content** instead. See the documentation.

Searches for files, folders, web links, and shared files across the users content or across the entire enterprise. See the documentation.

Uploads a small file to Box. See the documentation.

Update a file's content. See the documentation.

Adds a comment to a thread. See the documentation

Adds a contact to a specific static list. See the documentation

MCP and AI agents: **Prefer this action** when the user wants to **leave a note on a HubSpot contact** using a **contact ID** and note text. Exposes only hubspot, contactId, and noteBody (no engagement-type step, no reloadProps, no dynamic HubSpot schema fields). Do **not** use **Create Engagement** for this workflow. For every writable note property or non-contact associations, use **Create Note** instead. See the documentation

Archives a thread (soft delete). The thread is hidden from active views but can be restored via the HubSpot UI or by listing archived threads. See the documentation

Create a batch of companies in Hubspot. See the documentation

Create or update a batch of contacts by its ID or email. See the documentation

Update a batch of companies in Hubspot. See the documentation

Upsert a batch of companies in Hubspot. See the documentation

Clone a marketing email in HubSpot. See the documentation

Clone a site page in Hubspot. See the documentation

Create a new workflow. See the documentation

Create an association (link) between two CRM records. For example, associate a contact with a company, a deal with a contact, or a ticket with a company. Common association type IDs: contact→company (1), company→contact (2), deal→contact (3), contact→deal (4), deal→company (5), company→deal (6), ticket→contact (15), contact→ticket (16), ticket→company (26), company→ticket (25). See the documentation

Create associations between objects. See the documentation

Creates a new blog post in HubSpot. See the documentation

Create a WhatsApp, LinkedIn, or SMS message. See the documentation

Create a company in Hubspot. See the documentation

Create a contact workflow in Hubspot. See the documentation

Create a new CRM record (contact, company, deal, ticket, etc.). Pass property values as a JSON object in the properties parameter. Use **Search Properties** to discover available fields for the object type, **Get Properties** to find valid enum values (e.g. lifecyclestage, dealstage), and **List Pipelines and Stages** to find valid pipeline/stage IDs for deals and tickets. Use **List Owners** to find valid hubspot_owner_id values. See the documentation

Create a new custom object in Hubspot. See the documentation

Create a deal in Hubspot. See the documentation

Create a **task, meeting, email, call, or note** engagement with optional associations. Set **Engagement Type** and pass engagement fields in **Object Properties** (HubSpot property names, e.g. hs_note_body for notes). No reloadProps step and no **CONFIGURE_COMPONENT** requirement: association fields accept raw HubSpot IDs (use **Search CRM** or the Associations API to resolve associationType when needed). For **only** a note on a contact by ID, **Add Note to Contact** (hubspot-add-note-to-contact) is still simpler. See the documentation

Create a form in HubSpot. See the documentation

Create a landing page in Hubspot. See the documentation

Create a lead in Hubspot. See the documentation