Teams that keep HubSpot as their CRM can move lead routing and meeting scheduling from HubSpot’s
meetings tool and workflows to Default. HubSpot stays the system of record, and Default reads and
writes HubSpot contacts, companies, and deals, picks owners from queues, and books meetings
on your reps’ calendars.
This guide is for admins. It covers HubSpot scheduling pages, forms that redirect to a scheduling
page, and workflows that use the Rotate record to owner action. Default does not import these, so
plan to rebuild them.
HubSpot and Default at a glance
HubSpot scheduling pages in Default
HubSpot Rotate record to owner in Default
The Rotate record to owner workflow action assigns HubSpot records to users or teams in turn. In
Default, a workflow starts when HubSpot creates the record, a queue picks the member, and
Update Record writes the owner.
Replace a form redirect to a scheduling page
This example replaces a HubSpot form that redirects to a round robin scheduling page with
Prioritize contact owner turned on. Known contacts book with their owner, and new contacts book
through a queue of account executives named Inbound AEs.
Add the HubSpot form to Default
Open Signals, select Add Domain, and install the Pixel snippet on your site. Then open the
domain’s menu, select Catalog forms, add the HubSpot form, and map its fields. Default
recognizes embedded HubSpot forms. See Your forms. Start from the form
In Workflows, create a workflow and add the Form Submission trigger. Set
Connected Form to the form.
Look up the contact
Add Match Record with CRM set to HubSpot and Record set to Contact, matched on
email.
Book known contacts with their owner
On Match, add Display Scheduler with a Team event. Turn off Use event hosts and set
the host to the matched contact’s Contact owner.
Book new contacts through the queue
On No Match, add Display Scheduler with a Team event that the Inbound AEs queue
hosts. Keep Use event hosts on, so the queue picks the rep.
Test and publish
Select Test, then Run Test for a known contact and for a new contact. Then select
Publish, and turn on the deployment switch so the status
reads Live.
To send visitors to different scheduling pages by their answers, the way conditional redirects do,
add a Multi-Branch node before the Display Scheduler nodes, with 1 branch for each
condition.
Replace Rotate record to owner
This example replaces a HubSpot workflow that rotates new contacts across a sales team.
Add the trigger
In Workflows, create a workflow and add the CRM Record Created trigger. Set CRM to
HubSpot and Record to Contact. Add a Condition if only some contacts should route.
Pick the owner
Add Round-Robin and set Queue to your team’s queue.
Write the owner
Add Update Record with Platform set to HubSpot and Record Type set to Contact.
Choose the contact from the trigger, add Contact owner under Fields, and set it to
Latest assigned user.
Test and publish
Select Test, then Run Test with a test contact, and confirm the contact owner changed in
HubSpot. Then select Publish, and turn on the
deployment switch so the status reads Live.
A workflow test performs real actions. It updates HubSpot records and counts routing assignments.
Use a test contact.
Move from HubSpot routing and meetings to Default step by step
Connect HubSpot and your conferencing tool
Select Settings in the sidebar, then Integrations under Workspace Settings, and
connect HubSpot. See HubSpot. If your team meets on Zoom,
connect Zoom once for the workspace. Google Meet and Microsoft Teams links come from each member’s
own calendar connection. Invite your team and connect calendars
In Settings → Users, select Invite People. Each member connects Google Calendar or
Outlook Calendar and sets working hours. See Member onboarding. Map each rep to their HubSpot owner
In Settings → Users, add each rep’s HubSpot Owner ID. Default needs this mapping to write
HubSpot owners and to use a contact owner as a meeting host. See Users. Create policies and queues
In Routing → Policies, select Create Policy. Include Objects in
Assignment Units to replace Rotate record to owner, and Meetings to replace round robin
scheduling pages. In Routing → Queues, select Create Queue for each team. See
Policies and Queues. Rebuild scheduling pages as events
In Scheduling → Event Types, select Create new event. Use a Team event with a queue
as host for each round robin page, and ask each rep to create a Quick event for their personal
page. Assign reminder and notification templates under Messages. See Events. Rebuild form redirects and rotation workflows
Log meetings in HubSpot
Build a workflow with the Meeting Status trigger set to Booked. Find the contact with
Match Record, then add Create Engagement with Engagement type set to Meeting.
Switch over
When each Default workflow passes its tests, publish it and set it live. Then turn off the
HubSpot workflow that rotated the same records, so 2 tools do not assign the same contact. Remove
the scheduling page redirect from the form, and turn off or delete the HubSpot scheduling pages
you replaced. Share Default booking links in their place.
What does not carry over from HubSpot routing and meetings
- Configuration. Default has no importer for HubSpot scheduling pages, form redirects, or
workflows. You rebuild them in Default.
- Meetings already booked. Meetings booked through HubSpot scheduling pages stay in HubSpot.
Default’s Meetings list starts with the first meeting booked through Default.
- Meeting logging. Default writes meetings to HubSpot through a workflow you build, with
Create Engagement.
- Ticket and chat routing. Default routes HubSpot contacts, companies, and deals. It does not
route tickets or chat conversations.
- Custom user properties in round robin. Default can write any user property, but only the owner
property counts toward a queue’s round robin.
- Existing scheduling page links. Links you shared keep pointing at HubSpot. Replace them with
Default booking links.
Related: Default vs HubSpot