Connect HubSpot to Linear (OAuth)

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

Create a comment in Linear. See the documentation

Create an initiative in Linear. See the documentation.

Creates a new issue in Linear. Requires team ID and title. Optional: description, assignee, project, state. Returns response object with success status and issue details. Uses OAuth authentication. See Linear docs for additional info here.

Create a project in Linear. See the documentation.

Retrieve rich context about the authenticated Linear user, including core profile fields, recent timestamps, direct team memberships, and high-level organization settings. Returns the user object, a paginated team list (with names, keys, cycle configs, etc.), associated team memberships, and organization metadata such as auth defaults and SCIM/SAML flags. Use this when your workflow or agent needs to understand who is currently authenticated, which teams they belong to, or what workspace policies might influence subsequent Linear actions. See Linear's GraphQL viewer docs here.

Retrieves a Linear issue by its ID. Returns complete issue details including title, description, state, assignee, team, project, labels, and timestamps. Uses OAuth authentication. See Linear docs for additional info here.

Retrieves all teams in your Linear workspace. Returns array of team objects with details like ID, name, and key. Supports pagination with configurable limit. Uses OAuth authentication. See Linear docs for additional info here.

Get issues from a custom view in Linear. See the documentation.

List comments in Linear. See the documentation.

List initiatives in Linear. See the documentation.

List projects in Linear. See the documentation.

List views in Linear. See the documentation.

List workflow states (statuses) in Linear. Returns state IDs, names, types (e.g. backlog, started, completed, cancelled), and team info. Optionally filter by team. Uses OAuth authentication. See the documentation.

Remove a label from an issue in Linear. See the documentation.

Searches Linear issues by team, project, assignee, labels, state, or text query. Supports pagination, ordering, and archived issues. Returns array of matching issues. Uses OAuth authentication. See Linear docs for additional info here.

Update an initiative in Linear. See the documentation.

Updates an existing Linear issue. Can modify title, description, assignee, state, project, team, labels, priority, and dates. Returns updated issue details. Uses OAuth authentication. See Linear docs for additional info here.