Two-way integration between HubSpot and Outlook
We automated the flow from a Calendly booking → HubSpot data → an Outlook calendar event → a personalized email with the right attachments. Managers no longer handle any of it by hand — and the client stopped paying for advanced HubSpot email features.
About the Project
The client wanted every meeting booked through Calendly to appear automatically in the corporate Outlook calendar and to come with an email carrying the right materials — pitch deck, documents, brief, or call memo. All of it had to work without manual sending, without file loss, and without relying on expensive HubSpot email add-ons. The service had to behave as a process: one booking equals one event and one email, with logic for different meeting types.
About Customer
Arvid is a London-based customer-acquisition consultant and practitioner who helps companies rebuild marketing and sales for an AI-shifted market. His work centers on cutting manual routine, making processes manageable, and pushing CRM data accuracy up. He came to us through a partner referral with a concrete request: automate meeting operations and lead communication so calendar and email handling no longer depend on human discipline. After the first project, the collaboration turned into an ongoing one.
Three systems in one flow
Calendly creates the booking, HubSpot stores the contact and context, Outlook has to become the source of truth for both calendar and email. The three had to connect so that participants, time zones, and meeting types never get lost in transit.
Attachments as a rule-based mechanism
Files had to be selected automatically by scenario — meeting type, stage, label, or product — and always be the current version.
Idempotency
HubSpot workflows can restart, records get updated, Calendly resends webhooks. The system had to refuse to create two events or two emails for the same meeting.
Correct time zones
In real life, meetings get rescheduled. The integration had to update the existing event correctly and handle cancellations cleanly.
Manageability
Marketing and sales had to be able to change invite copy and attachment sets on their own — without any risk of breaking the process.
Transparency
If something failed, the team needed to see exactly which step broke, why, and what to do next.
Proposed Solution
HubSpot stays the source of data and rules. Outlook becomes the source of truth for calendar and email. The trigger fires from a HubSpot workflow after a booking or update, and a Node.js connector talks to Microsoft Graph to create or update the Outlook event and send a personalized email with attachments selected by rules stored in HubSpot.
Orchestration in HubSpot workflows
To keep the process managed from CRM, we configured the chain: trigger on meeting creation or update → data preparation → connector call → result and log written back into HubSpot properties.
Node.js connector between HubSpot and Microsoft Graph
The connector receives the meeting context from HubSpot, maps the fields, talks to Microsoft Graph, and returns statuses back to HubSpot — created, updated, failed — with the details attached.
Outlook event as the source of truth
The event is created with the correct subject, description, participants, and time zone. If the meeting is rescheduled, the integration updates the existing event instead of spawning a new one.
Email through Outlook with rule-based attachments
The email is generated from a template using context variables, links, and the right attachment set. Files are pulled from a controlled location, so the team never moves them by hand.
Managing files and templates without developers
We structured HubSpot with the fields, dictionaries, file links, and attachment rules — so a manager can update copy or swap a document once, and the change applies to every meeting that follows.
Idempotency, retries, and logging
Meeting-identification keys block duplicate events and emails when a workflow re-runs. Retry handling absorbs transient failures, and structured logs make the failure reason visible the moment something stops working.
We started by defining how the team worked after a booking — where the data came from, who created the event, where the email copy lived, how attachments got picked, and where mistakes most often crept in (time zone errors, wrong files, forgotten emails, duplicate events). We also listed the meeting types and the content differences between them.
Results
After launch, the client got a managed meeting-automation flow that takes manual work out of invite handling and shrinks the mistake surface around calendars, files, and email.
Zero manual invites
the meeting is created automatically after the booking
Up to 15 minutes
saved per meeting through automated setup
0.5–1.5 working hours
returned to the team each week at a volume of 30–50 calls
Zero confusion around attachments
files are selected automatically by rule
Fewer time-zone and reschedule issues
the Outlook event is updated, not duplicated
Budget saved
by moving invite and email logic into Outlook instead of paying for advanced HubSpot email features
Get in Touch
Or send us a message and we'll get back to you within 15 minutes during business hours