Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
HubSpot CRM
MOCO

Connect HubSpot CRM and MOCO integrations

Explore ready-made HubSpot CRM and MOCO templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate HubSpot CRM with MOCO and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

HubSpot CRM
Trigger: Watch Companies
MOCO
Action: Select an action
1. Select a trigger

  • Triggers when a new company is created.

  • Triggers when a contact is created, deleted, merged, restored, association changed, or deleted for privacy.

  • Triggers when a new contact is created.

  • Triggers when a new contact is added to a list (only for users with the paid Marketing account). This module will be deprecated on September 30th 2025.

  • Triggers when a CRM object is created/updated.

  • Triggers when a new deal is created.

  • Triggers when a new engagement is created in a portal. This endpoint will only return records created in the last 30 days, or the 10k most recently created records.

  • Triggers when a new file is stored in file manager.

  • Triggers when a new member is added to selected list.

  • Triggers when a new notification about changes is sent. This module can be used only with a developer connection where your user identifier, your Hubspot API Key, your Client ID, and Client Secret are filled in advanced parameters. You can have only one webhook URL per developer application. You can create more subscriptions for this one webhook.

  • Triggers when data is submitted from a given form.

  • Triggers when a new email timeline subscription added for the portal.

  • Triggers when a new ticket is created.

2. Select an action

  • Creates a new comment.

  • Creates a new company.

  • Creates a new contact.

  • Creates a new lead.

  • Creates a new presence.

  • Creates a new project.

  • Creates a new project expense.

  • Creates a new purchase.

  • Creates a new task on the selected project.

  • Creates a new user.

  • Creates a new invoice.

  • Creates a new invoice payment.

  • Deletes the selected comment.

  • Deletes the selected presence.

  • Deletes an existing project expense. Deletions are only possible if this entry is not yet billed.

  • Deletes an existing project task. Deleting a task on a project is only possible as long as no hours were tracked on this task.

  • Deletes the selected purchase. It's possible only if the status is pending and no payments have been registered.

  • Deletes the selected user. Deleting a staff member is only possible if no hours are billed already.

  • Deletes the selected invoice payment.

  • Returns information about the selected comment.

  • Returns information about the selected company.

  • Returns information about the selected contact.

  • Returns information about the selected lead.

  • Returns information about the selected presence.

  • Returns information about the selected project.

  • Returns information about the selected project expense.

  • Returns information about the selected project task.

  • Returns information about the selected purchase.

  • Returns information about the selected purchase category.

  • Returns information about the selected user.

  • Returns information about the selected invoice.

  • Returns information about the selected invoice payment.

  • Returns a PDF of an invoice.

  • Performs an arbitrary authorized API call.

  • Updates the selected comment.

  • Updates the selected company.

  • Updates the selected contact.

  • Updates the selected lead.

  • Updates the selected presence.

  • Updates the selected project.

  • Updates the selected project expense. Updates are only possible if this entry is not yet billed.

  • Updates the selected project task.

  • Updates status of the selected purchase.

  • Updates the selected user.

  • Updates the selected invoice payment.

  • Updates status of the selected invoice.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between HubSpot CRM and MOCO.

Add a Contact to a Workflow (Legacy)
Adds a contact to a specific workflow.
Action
Add Contacts to a List (Deprecated)
Adds contact records that have already been created in the system to a contact list. This module will be deprecated on September 30th 2025.
Action
Add Members to a List (Segment)
Adds records to selected list (segment).
Action
Create a Call
Creates a call with the given properties and returns a copy of the object, including the ID.
Action
Create a Comment
Creates a new comment.
Action
Create a Communication
Creates a communication with the given properties and returns a copy of the object, including the ID.
Action
Create a Company
Creates a company with the given properties and returns a copy of the object, including the ID.
Action
Create a Company
Creates a new company.
Action
Create a Contact
Creates a contact with the given properties and returns a copy of the object, including the ID.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.