When a new Nutshell form submission arrives, create a HubSpot CRM contact and alert sales in Slack

Each response to a Nutshell form creates a contact in HubSpot CRM and then posts a message to a Slack channel, so the lead is recorded and your sales team hears about it in one run.

Nutshell

HubSpot CRM

Slack

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 1.6k sites Free to import

The When a new Nutshell form submission arrives, create a HubSpot CRM contact and alert sales in Slack workflow on the FlowMattic canvas, with 3 steps across Nutshell, HubSpot CRM, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Some teams collect leads with Nutshell's forms but keep marketing in HubSpot and talk in Slack. Without a link, each response needs copying into HubSpot and a note to the sales channel. This workflow does both in order.

The Nutshell trigger fires when a form response is submitted. FlowMattic passes the answers to HubSpot CRM, where Create Contact adds the person. The run then moves to Slack and Send Channel Message posts the alert you write to the channel you pick, with values from the form and from HubSpot's reply.

The Slack step runs even if HubSpot refuses the contact, for example over an email it already holds. Task History shows the HubSpot error for that run, and the sales channel still gets the alert. Write the message so reps know to check HubSpot.

Demo requests from a website form

A Nutshell form on your site takes demo requests. Each one becomes a HubSpot contact for nurturing, and the sales channel hears about it right away.

Event sign-ups shared with sales

Attendees register through a Nutshell form. Marketing has them in HubSpot, and reps see each name in Slack to plan conversations at the event.

Partner referral form

Partners refer clients through a Nutshell form that asks who sent them, and the Slack post tells the partnerships lead which partner each referral came from.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Nutshell New Form Submission
Runs when a response is submitted to your Nutshell form. The answers are passed on to the HubSpot and Slack steps.
Step 2Action
HubSpot CRM Create Contact
Creates a HubSpot contact from the form response. Connect your HubSpot account and map the respondent's email and name into the contact.
Step 3Action
Slack Send Channel Message
Posts an alert to the Slack channel you choose. Write the message and include form answers, such as the person's name and company, so reps can act on it.

What you need

FlowMatticCore
Nutshell AccountAccount
HubSpot CRM AccountAccount
Slack AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Put the respondent's email and the form's main question in the Slack message, so reps don't need to open Nutshell or HubSpot to judge the lead.
To alert one rep instead of the whole channel, swap the last step for Slack's Send Direct Message action. Private channels need Send Private Channel Message.
Submit a test response after import and map both steps from that sample, then check the contact in HubSpot and the post in Slack.

Questions about this workflow

What happens if the Nutshell respondent is already in HubSpot?

HubSpot may refuse a duplicate email because Create Contact doesn't update existing contacts. The Slack alert still posts, and Task History shows HubSpot's reply.

Does the Nutshell form response also become a Nutshell lead?

This workflow doesn't change anything in Nutshell. What Nutshell does with its own form responses depends on your Nutshell setup.

Can the Slack alert mention the HubSpot contact?

Yes. The Slack step comes after HubSpot, so you can map values from HubSpot's response into the message. A test run shows which values HubSpot returns.