Contact Creation
Receive contact.creation events after activation. The webhook provides the contact ID, portal ID and original occurredAt timestamp rather than the person’s name, email or profile.
Workflow template
Reserve a 15-minute Google Calendar follow-up block exactly 24 hours after a HubSpot contact is created. The event contains a contact ID and record link, with no profile copy, attendees or invitation updates.
How it works
Receive contact.creation events after activation. The webhook provides the contact ID, portal ID and original occurredAt timestamp rather than the person’s name, email or profile.
Create a 15-minute UTC event starting 24 hours after occurredAt. The title uses the contact ID and the description links to its HubSpot record. Attendees are empty and send_updates is none.
The result
Follow up HubSpot contact 200001
Start: 2026-11-16T10:00:00.123Z End: 2026-11-16T10:15:00.123Z Time zone: UTC New HubSpot contact Contact ID: 200001 Open contact: https://app.hubspot.com/contacts/123456/record/0-1/200001 Review the contact and decide the next step before reaching out. Contact profiles, notes and attachments stay in HubSpot.
Start and end show the exact UTC formula output for the sample webhook; this is not a native calendar readback. No attendees or invitation updates are configured. Calendar visibility and default reminders still apply.
Before activation
Use the prepared Contact Creation event and decide which calendar should hold CRM follow-ups. The recipe receives record IDs rather than fetching contact profiles.
Connect Google Calendar and select a destination you can write to. Review visibility and reminder defaults; keep attendees empty and invitation updates set to none.
The Start and End formulas use occurredAt plus 86400 and 87300 seconds. Adjust them if needed, then activate and verify a fictional contact’s 15-minute block in a calendar you control.
Timing uses the original event, not delivery time. The block starts exactly 24 hours after occurredAt in UTC, including weekends. No business-hours, holiday or availability check is configured; delayed events can produce blocks in the past.
This does not send an invitation to the contact. Attendees are empty and send_updates is none. Calendar access and default reminders still apply. Only contact ID and a HubSpot link are copied, without names, email addresses, notes or attachments.
Follow-up scheduling is one-way. Existing contacts, later edits, merges and deletions are not synchronized. The record link requires HubSpot access. Reruns or ambiguous provider failures can create duplicate calendar events.
It starts 24 hours after the original HubSpot occurredAt timestamp and lasts 15 minutes. The formulas calculate UTC times, include weekends and do not check calendar availability or business hours.
No attendees are added and invitation updates are disabled. The contact is not emailed by this recipe; calendar visibility and its normal reminder defaults still apply.
The prepared webhook supplies record IDs, and the event uses the contact ID and record link. No contact profile is fetched and no name, email, notes or attachments are copied.
Timing still uses the original event timestamp, so a delayed notification can create a block in the past. Manual reruns or ambiguous failures can create duplicates; edits, merges and deletions do not update the calendar block.