Skip to main content

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

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

Connect remberg and HubSpot CRM

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

Get started free

Create a custom workflow

Integrate remberg 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
remberg
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

  • Updates the status of a specific work request by its remberg id.

  • Updates the status of a specific work request by its reference.

  • Creates a new contact.

  • Creates a new failure type.

  • Creates a new folder.

  • Creates a new part.

  • Creates a new part inventory by remberg ids.

  • Creates a new part inventory by number.

  • Creates a new ticket.

  • Creates a new work order.

  • Creates a new stock change in a work order by its remberg id.

  • Creates a new stock change in a work order by its reference.

  • Creates a new work request.

  • Creates a new asset.

  • Creates a new asset type.

  • Creates a new organization.

  • Updates the status of a specific work request by its remberg id.

  • Updates the status of a specific work request by its reference.

  • Deletes a specific contact by its remberg id.

  • Deletes a specific failure type by its reference.

  • Deletes a specific file or folder by its remberg id.

  • Deletes a specific ticket by its remberg id.

  • Deletes a specific work order by its remberg id.

  • Deletes a specific work order by its erp reference.

  • Deletes a specific work request by its remberg id.

  • Deletes a specific work request by its erp reference.

  • Deletes a specific asset by its remberg id.

  • Deletes a specific asset by its number.

  • Deletes a specific asset type by its remberg id.

  • Deletes a specific asset type by its label.

  • Deletes a specific organization by its remberg id.

  • Deletes a specific organization by its number.

  • Downloads binary of a specific file by its remberg id.

  • Gets a specific contact by its remberg id.

  • Gets a specific file by its remberg id.

  • Gets a specific file by its path.

  • Gets a specific form by its remberg id.

  • Gets a specific part by its remberg id.

  • Gets a specific part by its number.

  • Gets a specific ticket by its remberg id.

  • Gets a specific ticket's conversations by its remberg id.

  • Gets a specific work order by its remberg id.

  • Gets a specific work order by its erp reference.

  • Gets the time entries of a specific work order by its remberg id.

  • Gets a specific work request by its remberg id.

  • Gets a specific work request by its reference.

  • Gets a specific asset by its remberg id.

  • Gets a specific asset by its number.

  • Gets a specific asset type by its remberg id.

  • Gets a specific asset type by its label.

  • Gets a specific inventory for part and asset by their remberg ids.

  • Gets a specific inventory for part and asset by their numbers.

  • Gets a specific organization by its remberg id.

  • Gets a specific organization by its number.

  • Updates a specific contact by its remberg id.

  • Updates a specific failure type by its reference.

  • Updates a specific file or folder by its remberg id.

  • Updates binary content of specific file by its remberg id.

  • Updates a specific part by its remberg id.

  • Updates a specific part by its number.

  • Updates a specific ticket by its remberg id.

  • Updates a specific work order by its remberg id.

  • Updates a specific work order by its erp reference.

  • Updates a specific work request by its remberg id.

  • Updates a specific work request by its reference.

  • Updates a specific asset by its remberg id.

  • Updates a specific asset by its number.

  • Updates a specific asset type by its remberg id.

  • Updates a specific asset type by its label.

  • Updates a specific organization by its remberg id.

  • Updates a specific organization by its number.

  • Uploads a new file.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between remberg 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
Approve a work request by id
Updates the status of a specific work request by its remberg id.
Action
Approve a work request by reference
Updates the status of a specific work request by its reference.
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 new contact.
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.