Skip to main content

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

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

Connect Qontext and HubSpot CRM

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

Get started free

Create a custom workflow

Integrate Qontext with HubSpot CRM 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
Qontext
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 file at the given path, or inside a folder by its ID. A path already holding a file is a conflict, so nothing is overwritten.

  • Creates a folder at the given path, creating any missing parent folders, or inside a parent folder by its ID.

  • Deletes a file, addressed by ID or by path, along with its change history. A protected file, or one with changes in review, is refused. This action cannot be undone.

  • Deletes a folder, addressed by ID or by path. A folder that still has contents is refused unless Recursive is enabled. This action cannot be undone.

  • Returns a file with its full content, addressed by ID or by path. A file in another workspace answers as not found, so its existence does not leak.

  • Returns a folder, addressed by ID or by path. A folder in another workspace answers as not found, so its existence does not leak.

  • Performs an arbitrary authorized API call.

  • Renames a file, moves it to another folder, or sets whether writes to it go to review. Accepts one of the three per call. Addressed by ID or by path.

  • Replaces the whole content of a file, addressed by ID or by path. Takes the change the edit started from, so a concurrent edit is not overwritten silently.

  • Renames a folder in place, or moves it and everything below it into another folder. Addressed by ID or by path. Every ID in the subtree survives a move.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Qontext and HubSpot CRM.

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 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 Contact
Creates a contact with the given properties and returns a copy of the object, including the ID.
Action
Create a Custom Object Record
Creates a custom object with the given properties and returns a copy of the object, including the ID.
Action
Create a Deal
Creates a deal 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.