HubSpot · Gmail
Send Gmail notifications for new HubSpot contacts
Email a selected reviewer when a new contact is created in HubSpot. Use this to notify an onboarding owner who follows CRM intake from their inbox. Connect HubSpot and Gmail, enter a fixed recipient address, then test with one fictional contact. Each plain-text email includes the contact ID, HubSpot account ID, creation event ID and a direct link to the CRM record. The instant trigger listens only for contact.creation events received after activation. Includes its own fictional contact-created example. HubSpot creation webhooks provide record IDs, not the complete contact profile, so contact names, email addresses, company details and other properties are not copied. Opening the record link requires existing HubSpot access. Existing contacts, later property edits, merges and deletions are not imported or synchronized. The recipient is configured by you; this does not email the new contact or send a marketing campaign. No contact permissions are changed. Emails are sent from the connected Gmail account and appear in Sent. No HTML, Cc, Bcc or attachments are configured. Gmail limits apply; manual reruns or ambiguous provider retries can resend a notification. Use your own email address for the first test.
- 1. HubSpot · Contact Creation
- 2. Gmail · Email the new HubSpot contact notification
View template →Use templateHubSpot · Google Drive
Create Google Drive folders for new HubSpot contacts
Prepare an empty document folder whenever a new contact is created in HubSpot. Connect HubSpot and Google Drive, optionally browse to a writable parent folder, then publish. Without a parent folder, the folder is created in My Drive. Names follow HubSpot {portal ID} - Contact {contact ID}, so contacts from different accounts remain distinguishable. HubSpot creation webhooks provide IDs, not contact names or email addresses. Includes its own fictional contact-created example. Only contact.creation events received after activation are processed; existing contacts and later edits, merges or deletions are not synchronized. This creates folders only: it does not copy documents, attach the folder to the CRM record, invite the contact or change sharing permissions. Access follows the destination folder. Test with one fictional contact first. Manually rerunning an event can create another folder with the same name.
- 1. HubSpot · Contact Creation
- 2. Google Drive · Create contact document folder
View template →Use templateHubSpot · Google Sheets
Log new HubSpot contacts in Google Sheets
Log each new HubSpot contact in a Google Sheets worksheet. Connect HubSpot and Google Sheets, then browse to your spreadsheet and worksheet. Append Values writes five columns in this order: A Contact ID, B HubSpot record URL, C Event time (Unix milliseconds), D Event ID, E Portal ID. An empty worksheet works; optional headers can be added in row 1 before activation. Values are written as RAW data and new rows are inserted after the existing table. Only contact.creation events received after activation are processed. Existing contacts and later edits, merges or deletions are not synchronized. HubSpot creation webhooks contain record IDs, not names or email addresses, so contact profile fields are not included. The CRM link requires existing HubSpot access. Includes its own fictional event sample. Test with one fictional contact first.
- 1. HubSpot · Contact Creation
- 2. Google Sheets · Log the new HubSpot contact
View template →Use templateHubSpot · Telegram Bot
Send Telegram alerts for new HubSpot contacts
Receive a Telegram notification whenever a new contact is created in HubSpot. Connect HubSpot and Telegram, then select a chat where your bot can post. Each message contains the contact ID and a direct link to its HubSpot record. Only contact.creation events received after activation are processed; existing contacts, later edits, merges and deletions are not announced. Creation webhooks provide record IDs, not contact names or email addresses, so profile fields are not copied. Opening the CRM link requires existing HubSpot access. Includes its own fictional contact-created example. Choose a chat appropriate for CRM notifications. Test with one fictional contact first. This workflow sends alerts to the selected chat, does not message the contact directly, and does not change CRM permissions.
- 1. HubSpot · Contact Creation
- 2. Telegram Bot · Notify the CRM alerts chat
View template →Use templateHubSpot · Notion
Create Notion follow-up pages for new HubSpot contacts
Create a Notion follow-up page when a new contact is created in HubSpot. Connect HubSpot and Notion, then browse to an accessible parent page. Each child page includes the contact ID, a direct link to its HubSpot record and editable Overview, Notes and Follow-up sections. Uses the visual page content editor. Only contact.creation events received after activation are processed; existing contacts, later edits, merges and deletions are not imported or synchronized. Creation webhooks provide record IDs, not the full contact profile, so names and email addresses are not copied. Opening the CRM link requires existing HubSpot access. Includes its own fictional contact-created example. Access follows the selected Notion parent; choose one appropriate for CRM notes. This creates child pages, not database rows, and does not contact the person or change CRM permissions. Test with a fictional contact first.
- 1. HubSpot · Contact Creation
- 2. Notion · Create a CRM follow-up page
View template →Use templateHubSpot · Trello
Create Trello follow-up cards for new HubSpot contacts
Create a Trello follow-up card whenever a new contact is created in HubSpot. Connect HubSpot and Trello, then browse to a board and list. Each card contains the contact ID, a direct HubSpot record link and an editable follow-up plan. Only contact.creation events received after activation create cards; existing contacts, later edits, merges and deletions are not imported or synchronized. HubSpot creation webhooks provide record IDs, not contact names or email addresses, so these profile fields are not copied. Opening the record link requires existing HubSpot access. Includes its own fictional contact-created example. Choose a board appropriate for CRM follow-up and test with one fictional contact first. This workflow does not contact the person, assign an owner automatically, or change CRM permissions.
- 1. HubSpot · Contact Creation
- 2. Trello · Create a CRM follow-up card
View template →Use templateHubSpot · Slack
Send Slack alerts for new HubSpot contacts
Notify a Slack channel when a new contact is created in HubSpot. Connect HubSpot and Slack, then browse to a channel where the FastHook bot can post. Each message contains the contact ID and a direct link to its HubSpot record. The instant trigger listens only for contact.creation events after activation. Existing contacts, property edits, merges and deletions are not announced. HubSpot creation webhooks contain record IDs, not the full contact profile, so names, emails and other contact properties are not copied. Opening the link requires existing HubSpot access. Includes its own fictional contact-created example. Choose a channel appropriate for CRM notifications. Test with one fictional contact first; this template does not create contacts, send marketing emails or change contact permissions.
- 1. HubSpot · Contact Creation
- 2. Slack · Notify the CRM contacts channel
View template →Use templateStripe · HubSpot
Create HubSpot contacts for new Stripe customers
Create one HubSpot contact from the email address on each new Stripe customer. Connect Stripe and HubSpot, then activate the workflow. Customers without an email address are skipped. Use a valid unique email; invalid or existing emails may fail, and this template does not upsert or update contacts. The customer.created event is the only trigger. Creating a customer does not confirm a payment or subscription. No marketing subscriptions are configured. Historical customers are not imported and later customer updates are not synchronized. Includes a fictional English sandbox example for Lina Müller using a valid example.com address. Only email is copied; names, phone numbers, addresses, metadata and payment details are not transferred. Test with a fictional Stripe sandbox customer first.
- 1. Stripe · Customer Created
- 2. HubSpot · Create CRM contact
View template →Use templateGoogle Sheets · HubSpot
Create HubSpot contacts from new Google Sheets rows
Turn new spreadsheet leads into HubSpot contacts. Use Email, FirstName, LastName and Company headers in row 1, then append one complete contact per row. Connect Google Sheets and HubSpot, select the spreadsheet and worksheet, and keep the prepared property mappings. Use a valid, unique email for each new contact. This template creates contacts; it does not update existing contacts or merge duplicate emails. HubSpot may reject a contact whose email already exists. Activate and let the first poll establish a baseline before appending rows. Existing rows and later edits are not imported; avoid deleting or reordering rows while active. Includes a fictional English example with German characters. No marketing subscription or email campaign is configured by this template. Contact data is copied to the connected HubSpot account.
- 1. Google Sheets · New Row Added
- 2. HubSpot · Create CRM contact
View template →Use template
