Skip to main content

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

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

Connect DNCSolution and HubSpot CRM

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

Get started free

Create a custom workflow

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

  • The Initiate step begins the bulk scrub process. Valid requests receive an HTTPS 200 - OK response including an access token. The access token is required to stage, execute, and retrieve the status of the bulk scrub. It is active for a day, and once expired, it cannot be used again.

  • The staging step is the second step in the bulk scrub process where the data gets staged for execution. The staging step can be performed multiple times prior to executing a bulk scrub, allowing you to stage large sets of data over time, as long as the access token remains active. For instance, you can initiate a bulk scrub early in the morning and stage data at multiple intervals throughout several hours. When the execute request is triggered, all the staged data will be scrubbed.

  • Once all the data is staged, run the execute request to begin scrubbing. Once this step is invoked, you can no longer stage additional data. All permissions are validated during this step.

  • Use this method to retrieve the current status of a bulk scrub.

  • Add numbers to your Do Not Contact lists.

  • Performs an arbitrary authorized API call

  • This method enables you to re-scrub a call list that was successfully executed using a valid and unexpired access token. Following the initial scrub, the rescrub is allowed based on the duration specified with the Initiate request. If this field is 0, or omitted, the access token is deactivated and the scrub data is deleted.

  • Remove numbers from your Do Not Contact lists.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between DNCSolution and HubSpot CRM.

1. Initiate bulk scrub
The Initiate step begins the bulk scrub process. Valid requests receive an HTTPS 200 - OK response including an access token. The access token is required to stage, execute, and retrieve the status of the bulk scrub. It is active for a day, and once expired, it cannot be used again.
Action
2. Stage phone numbers for bulk scrub
The staging step is the second step in the bulk scrub process where the data gets staged for execution. The staging step can be performed multiple times prior to executing a bulk scrub, allowing you to stage large sets of data over time, as long as the access token remains active. For instance, you can initiate a bulk scrub early in the morning and stage data at multiple intervals throughout several hours. When the execute request is triggered, all the staged data will be scrubbed.
Action
3. Execute bulk scrub
Once all the data is staged, run the execute request to begin scrubbing. Once this step is invoked, you can no longer stage additional data. All permissions are validated during this step.
Action
4. Bulk scrub status
Use this method to retrieve the current status of a bulk scrub.
Action
5. Get exception records
This method allows you to retrieve records that encountered exceptions during the staging process, enabling you to address and re-stage them for bulk scrub. Exceptions that occur during the execution step should also be retrieved using this endpoint.
Search
5. Get success records
This endpoint returns all scrubbed data that was successfully executed.
Search
Add a Contact to a Workflow (Legacy)
Adds a contact to a specific workflow.
Action
Add a number
Add numbers to your Do Not Contact lists.
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
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.