Add new Gripp companies as contacts in HubSpot CRM
Each company created in Gripp is added to HubSpot CRM as a new contact, using the company details you map, so the clients your agency sets up in Gripp also appear in the CRM your sales team uses.
Gripp
HubSpot CRM2 steps Setup ~5 min Used on 938 sites Free to import
What this workflow does
Agencies often run projects, hours and invoices in Gripp while sales and marketing live in HubSpot. When a new client is set up in Gripp, it is easy for HubSpot to miss it, and then the two systems disagree about who your clients are. This workflow sends each new Gripp company to HubSpot as it is created.
The Gripp trigger runs when a company is created and passes its details to FlowMattic. The HubSpot CRM step then uses Create Contact, so the company is added as a contact record, not as a HubSpot company. You map the Gripp values, such as the company's email address and name, into the contact.
HubSpot identifies contacts by email address, so map one wherever Gripp provides it. Create a test company in Gripp after import and check Task History to confirm what Gripp sends and how HubSpot responds.
New clients set up by the project office
The project office adds a client in Gripp before the first job starts. The client appears in HubSpot as a contact, so account managers can log calls and emails against it.
Marketing to existing clients
Every client company created in Gripp joins HubSpot, where marketing can include them in client newsletters and case study requests.
Freelancers and sole traders as clients
When many of your clients are one-person businesses, a HubSpot contact per Gripp company is a natural fit, since the company and the person are the same.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Gripp Company CreatedRuns when a new company is created in your Gripp account. The company details Gripp sends become available to map into the HubSpot contact.
- HubSpot CRM Create Contact
Creates a new contact in HubSpot CRM from the Gripp company. Connect your HubSpot account and map the company's email and name into the contact. A test run shows which values arrive.
What you need
- FlowMatticCore
- Gripp AccountAccount
- HubSpot CRM 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.
- If some Gripp companies have no email address, add a Filter after the trigger that continues only when the email value is not empty, so HubSpot is not sent incomplete contacts.
- Add a Slack message after HubSpot so your sales team knows a new client has been set up in Gripp.
- Create one test company in Gripp after import, then read the run in Task History to check the field names before mapping them into HubSpot.
Questions about this workflow
Why does this create a HubSpot contact rather than a HubSpot company?
The template uses HubSpot's Create Contact action, so each Gripp company becomes a contact record. If you want company records instead, replace the action with a company action in FlowMattic, if your HubSpot integration offers one.
What if the Gripp company already exists as a contact in HubSpot?
The step creates a contact, it does not look one up first. HubSpot may reject a contact whose email is already in use, and Task History shows that error on the HubSpot step.
Are companies created in Gripp before I import this sent to HubSpot?
No. Only companies created after the workflow is turned on start a run.
Does editing a company in Gripp update the HubSpot contact?
No. The trigger fires on new companies only, so later edits in Gripp are not sent to HubSpot.
More CRM & Contacts workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted