# Default

> This site documents Default, the platform for lead routing, scheduling, enrichment and workflows. If you're still on Default v1, use docs.default.com.

- [Default documentation](https://docs.os.default.com/index.md): Guides and reference for Default, the platform for lead routing, scheduling, enrichment, and workflows: set up a workspace, route leads, book meetings, and automate what happens next.
- [Introduction to Default](https://docs.os.default.com/overview/introduction.md): What Default does and how its parts fit together: lead routing, scheduling, forms and the Pixel, enrichment, workflows, the Chrome extension, the API, and the MCP server.
- [Default plans, limits, and what's included](https://docs.os.default.com/overview/plans-and-limits.md): How Default plans work, what uses enrichment credits and how many, and the hard limits in the product: the API rate limit, waterfall providers, booking guests, webhook size, and more.
- [Security and compliance in Default](https://docs.os.default.com/overview/security.md): How Default handles SOC 2, sign-in and single sign-on (SSO), roles, API keys, webhooks, MCP access, website visitor data, and SMS consent.
- [Default glossary](https://docs.os.default.com/overview/glossary.md): Definitions of the terms used in Default: queues, routing policies, round robin, weighting, tiebreakers, Rules of Engagement, events, workflows, triggers, nodes, waterfalls, credits, the Pixel, Reveal, and more.
- [Set up a new Default workspace](https://docs.os.default.com/get-started.md): Admin guide to setting up a new Default workspace: connect your CRM and conferencing tools, create a routing policy and a queue, and invite your team.
- [New member onboarding in Default](https://docs.os.default.com/member-onboarding.md): Set up your Default account as a new member: profile, availability, calendar connection, meeting location, notifications, and your first booking link.
- [Migrating to a new Default workspace](https://docs.os.default.com/migrate.md): What Default migrates into your new Default workspace, what your team re-establishes after the migration, and what works differently from the previous product.
- [Switch from Chili Piper to Default](https://docs.os.default.com/switching/chili-piper.md): Migration guide from Chili Piper to Default: how Concierge, Distro, Handoff, and ChiliCal map to Default workflows, queues, and events, the setup steps in order, and what has no direct equivalent.
- [Switch from LeanData to Default](https://docs.os.default.com/switching/leandata.md): Migration guide from LeanData to Default: how FlowBuilder graphs, Lead-to-Account matching, Round Robin pools, territories, and BookIt map to Default, the setup steps in order, and what has no direct equivalent.
- [Switch from Calendly to Default](https://docs.os.default.com/switching/calendly.md): Migration guide from Calendly to Default: how routing forms, round robin and collective event types, Workflows, and the Salesforce and HubSpot integrations map to Default, the setup steps in order, and what has no direct equivalent.
- [Switch from Cal.com to Default](https://docs.os.default.com/switching/cal-com.md): Migration guide from Cal.com to Default: how routing forms, round robin, collective, and managed event types, Workflows, embeds, and the Salesforce and HubSpot apps map to Default, the setup steps in order, and what has no direct equivalent.
- [Switch from RevenueHero to Default](https://docs.os.default.com/switching/revenuehero.md): Migration guide from RevenueHero to Default: how Inbound Routers, Matching and Distribution Rules, Relays, Campaign Routers, and enrichment map to Default, the setup steps in order, and what has no direct equivalent.
- [Switch from HubSpot routing and meetings to Default](https://docs.os.default.com/switching/hubspot.md): Migration guide for teams that keep HubSpot as their CRM and move lead routing and meeting scheduling to Default: how scheduling pages, form redirects, and the Rotate record to owner action map to Default, the setup steps in order, and what has no direct equivalent.
- [Guides for go-to-market motions in Default](https://docs.os.default.com/guides.md): Step-by-step guides for running go-to-market motions with Default workflows, routing, and scheduling: demo request routing, speed to lead, lead qualification, account-based routing, MQL to SQL handoff, SDR to AE handoff, product-qualified leads, event follow-up, closed-lost re-engagement, and handof…
- [Routing demo requests to a booked meeting with Default](https://docs.os.default.com/guides/demo-request-routing.md): How to route a demo request form to a booked meeting with Default: the Form Submission or API trigger starts a workflow, Multi-Branch and Enrich Data qualify the request, Match Record finds the existing account, and Display Scheduler books the account owner or the next rep in a round-robin queue, wi…
- [Automating speed to lead with Default: assign, alert, and escalate inbound leads](https://docs.os.default.com/guides/speed-to-lead.md): How to automate speed to lead and inbound lead response time with Default: a Form Submission or CRM Record Created trigger, Enrich Data, Round-Robin to an available rep, Update Record for the owner, and a Send Slack Message alert, then a Time Delay and a Match Record re-check that escalates any lead…
- [Account-based lead routing: sending leads to the account owner with Default](https://docs.os.default.com/guides/account-based-routing.md): How to route new leads and contacts from accounts you already work to the account owner with Default: a CRM Record Created or Form Submission trigger starts the workflow, Match Record finds the Salesforce Account or HubSpot Company by company domain, Update Record or a Rules of Engagement rule assig…
- [MQL to SQL: handing marketing-qualified leads to sales with Default](https://docs.os.default.com/guides/mql-to-sql-handoff.md): How to hand a marketing-qualified lead (MQL) to sales with Default: a CRM Record Updated trigger fires when a Salesforce Lead's status or a HubSpot Contact's lifecycle stage changes to MQL, Enrich Data fills gaps, Round-Robin or Rules of Engagement picks the rep, Update Record writes the owner, and…
- [SDR to AE handoff: booking the account executive's meeting from the Chrome extension](https://docs.os.default.com/guides/sdr-to-ae-handoff.md): How to run the sales development rep (SDR) to account executive (AE) handoff with Default: an admin builds a workflow with the Extension trigger and a Display Scheduler node that books a Team event hosted by the account executive queue, and SDRs route and book the account executive's meeting from Gm…
- [Routing product-qualified leads (PQLs) to sales with Default](https://docs.os.default.com/guides/product-qualified-leads.md): How to route product-qualified leads (PQLs) to sales with Default: product events from Segment, PostHog, Mixpanel, Amplitude, Hightouch, or Census start a workflow through the Incoming Webhook or API trigger, then Match Record, Enrich Data, Multi-Branch or AI Prompt, Round-Robin, Create Record, Upda…
- [Following up on trade show and event leads with Default](https://docs.os.default.com/guides/event-lead-follow-up.md): Follow up on trade show, conference, and webinar leads with Default: import the list into Salesforce or HubSpot, and a CRM Record Created trigger with a Condition starts a workflow that checks for existing records with Match Record, runs Enrich Data, routes each lead to the account owner or a Round-…
- [Re-engaging closed-lost deals in Salesforce and HubSpot with Default](https://docs.os.default.com/guides/closed-lost-re-engagement.md): Re-engage closed-lost opportunities and deals with Default: a CRM Record Updated trigger on a Salesforce Opportunity or HubSpot Deal with a Time Delay, or an Account Signal or Form Submission trigger, then Match Record to find the closed-lost deal and Send Slack Message to alert the rep who owned it…
- [Handing off closed-won deals from sales to customer success with Default](https://docs.os.default.com/guides/sales-to-customer-success-handoff.md): How to automate the sales to customer success handoff with Default: the CRM Record Updated trigger fires when a Salesforce Opportunity or HubSpot Deal reaches Closed Won, Round-Robin picks a customer success manager from a queue, Update Record writes them to the Account or Company, Create Slack Chan…
- [Send routed leads to sales sequences from Default](https://docs.os.default.com/guides/routed-leads-to-sequences.md): How Default adds a routed lead to a sequence in Apollo, Outreach, Salesloft, Amplemarket, Smartlead, Gong Engage, or HubSpot, with the assigned rep as the sender: supported tools, setup, an example workflow, and troubleshooting.
- [Website visitor to outbound in Default: identify, enrich, assign, sequence](https://docs.os.default.com/guides/website-visitor-to-outbound.md): Turn an identified website visitor into outbound with Default: Reveal identifies the visitor with Clearbit Reveal, Demandbase, or Vector, Enrich Data fills in the record, Round-Robin assigns a rep, and a sequencing node adds the person to the rep's sequence.
- [Default and Marketo: webhooks and Marketo forms](https://docs.os.default.com/guides/marketo.md): How Default works with Marketo: capture embedded Marketo forms with the Pixel, send Marketo leads to a Default workflow with a webhook, route leads when they reach a lead score threshold, and write results back to Marketo.
- [Default and Clay: webhooks and the API](https://docs.os.default.com/guides/clay.md): How Default and Clay connect by webhook: call a Default workflow from a Clay table through an incoming webhook or the API, send records from a Default workflow to a Clay table with Send to Webhook, and where each tool fits for inbound enrichment.
- [Company and person tables in Default](https://docs.os.default.com/tables.md): Tables in Default holds your workspace's company and person records and the data that fills them. Tables is in beta and available where enabled.
- [How enrichment waterfalls work in Default](https://docs.os.default.com/enrichment/waterfalls.md): How a Default enrichment waterfall uses Clearbit, Apollo, People Data Labs, and Wiza: provider order, what counts as a hit, how credits are charged, and who supplies the provider accounts.
- [HubSpot enrichment in Default](https://docs.os.default.com/enrichment/hubspot.md): Enrich HubSpot contacts and companies with Default when a form is submitted or a HubSpot record is created, then write the enriched fields back to HubSpot properties.
- [AI account research in Default with Deep Research and Parallel](https://docs.os.default.com/enrichment/ai-research.md): Research accounts on the live web inside a Default workflow with the Deep Research node, powered by Parallel, and when to use it instead of an enrichment waterfall.
- [Preventing and finding duplicate CRM records in Default](https://docs.os.default.com/enrichment/duplicates.md): How Default keeps workflows from creating duplicate Salesforce and HubSpot records, how it lists the duplicates you already have, and why merging stays in your CRM.
- [Backfilling missing CRM fields with Default](https://docs.os.default.com/enrichment/backfill.md): Fill empty fields on existing Salesforce and HubSpot records with Default enrichment, using Tables, a workflow on CRM record changes, or the API trigger.
- [How lead routing works in Default](https://docs.os.default.com/lead-routing.md): How Default picks an owner for each lead, CRM record, or meeting: queues, reusable routing policies, round robin, weighting, tiebreakers, eligibility checks, and the record of every assignment.
- [Lead routing queues in Default](https://docs.os.default.com/queues.md): How queues in Default group the people who receive leads, CRM records, and meetings: members, weights, calendar checks, calibration, ranking, assignments, and the activity log.
- [Lead routing policies in Default](https://docs.os.default.com/policies.md): How routing policies in Default set the rules a queue runs: assignment units, round robin and other distribution rules, tiebreakers, weighting, availability exclusions, and credits.
- [Rules of Engagement: how Default decides which queue or owner gets a lead](https://docs.os.default.com/rules-of-engagement.md): Rules of Engagement in Default runs a reusable ruleset from top to bottom, sends each lead to a queue, a user, or no one, falls back when a target can't be used, and logs every decision rule by rule.
- [Salesforce lead routing in Default](https://docs.os.default.com/lead-routing/salesforce.md): How Default routes Salesforce leads, contacts, accounts, and opportunities: the triggers that start routing, the queue that picks the owner, the Owner ID write-back, and the setup it needs.
- [HubSpot lead routing in Default](https://docs.os.default.com/lead-routing/hubspot.md): How Default routes HubSpot contacts, companies, and deals: the triggers that start routing, the queue that picks the owner, the HubSpot owner write-back, and the setup it needs.
- [Territory and segment routing in Default](https://docs.os.default.com/lead-routing/territories.md): Route leads by territory, region, segment, or company size in Default: 1 queue per territory team, chosen by Rules of Engagement, Multi-Branch conditions, or a territory value in your CRM, with existing account owners first.
- [Qualifying inbound leads automatically with Default](https://docs.os.default.com/lead-routing/qualification.md): How to qualify inbound leads automatically before they reach sales with Default: check for a work email, enrich the lead, test fit with Multi-Branch or Rules of Engagement, classify free text with AI Prompt, and show the scheduler only to qualified leads.
- [Lead scoring beyond native Salesforce scoring with Default](https://docs.os.default.com/lead-routing/lead-scoring.md): How to score or tier leads with Default workflows: rules-based fit tiers, AI Prompt classification, Deep Research scores, and scores your CRM already has, written back to Salesforce or HubSpot and used for routing in the same run.
- [Why a lead went to a rep: routing logs in Default](https://docs.os.default.com/lead-routing/logs.md): Trace any routing decision in Default: the assignment detail with scored members, tiebreaker, and determined member, the workflow run log, the Rules of Engagement evaluation log, and the routing activity log.
- [Salesforce lead-to-account matching in Default](https://docs.os.default.com/lead-routing/matching/salesforce-lead-to-account.md): How Default matches Salesforce leads to existing accounts: the Match Record node, matching by company domain, tiebreakers when several accounts match, the No Match branch, and converting the lead into the matched account.
- [Salesforce contact matching in Default](https://docs.os.default.com/lead-routing/matching/salesforce-contacts.md): How Default finds an existing Salesforce contact by email before it creates a lead, what to do on Match and No Match, and how Convert Lead merges a duplicate lead into that contact and its account.
- [HubSpot contact matching in Default](https://docs.os.default.com/lead-routing/matching/hubspot-contacts.md): How Default finds an existing HubSpot contact by email before it creates one: Match Record runs first because HubSpot's Create Record has no Update on conflict, what to do on Match and No Match, and what happens when 2 runs for the same email overlap.
- [HubSpot contact-to-company matching in Default](https://docs.os.default.com/lead-routing/matching/hubspot-contacts-to-companies.md): How Default finds the HubSpot company for a contact: Match Record on property values such as the company domain, Match by association from a contact an earlier step found, tiebreakers, the No Match branch, and Create Association.
- [Salesforce account and HubSpot company matching in Default](https://docs.os.default.com/lead-routing/matching/accounts-and-companies.md): How Default matches a company-level signal, such as an Account Signal website visit or a webhook that carries only a domain, to a Salesforce Account or HubSpot Company by domain, and routes it to the matched record's owner.
- [Scheduling event types in Default](https://docs.os.default.com/events.md): How to create Quick and Team events in Default: booking pages, hosts and queue hosts, availability, booking form questions, meeting messages, reminders, and booking links.
- [Meetings dashboard in Default](https://docs.os.default.com/meetings.md): How the Meetings dashboard in Default lists every meeting booked in your workspace: columns, filters, meeting details, no-shows, cancellations, reassignment, and the calendar view.
- [Meeting messages in Default](https://docs.os.default.com/scheduling-messages.md): How the Messages library in Default holds reusable email and SMS templates for meeting notifications and reminders, with variables, fallbacks, and branded email styling.
- [Round robin and group meetings in Default](https://docs.os.default.com/scheduling/round-robin-and-group-meetings.md): Book round robin meetings with a Team event hosted by a queue, choose how the booking page offers times with the Slots Rule, and book meetings with several hosts, optional teammates, fixed invitees, and guests.
- [Reducing no-shows with meeting reminders in Default](https://docs.os.default.com/scheduling/reminders-and-no-shows.md): How Default sends email and SMS meeting reminders to guests and hosts, how reps mark a no-show by hand, and what marking a no-show does: routing credit back to the rep, no-show messages, and a Meeting Status workflow trigger.
- [Following up with leads who didn't book a meeting in Default](https://docs.os.default.com/scheduling/follow-up-unbooked-leads.md): When a visitor submits a form but doesn't book, a Default workflow takes the Display Scheduler node's Not booked branch, where you can alert your team in Slack, assign an owner, create a CRM task, and add the lead to a sequence in Apollo, Outreach, Salesloft, Amplemarket, Smartlead, Gong Engage or H…
- [Handing off leads and meetings between reps in Default](https://docs.os.default.com/scheduling/rep-handoffs.md): How Default hands leads and meetings from 1 rep to another: a sales development rep books the account executive's meeting through a routing workflow, a rep reassigns a booked meeting from the meetings dashboard or the Chrome extension and the first rep gets routing credit back, or a workflow assigns…
- [Workflows in Default](https://docs.os.default.com/workflows.md): How workflows in Default automate what happens to inbound leads: triggers, nodes, testing, publishing, version history, and run logs.
- [Workflow node reference for Default](https://docs.os.default.com/workflows/node-reference.md): Every node you can add to a workflow in Default, grouped by job: actions, CRM records, sequencing, notifications, enrichment, AI, routing, scheduling, and logic.
- [Workflow triggers in Default](https://docs.os.default.com/workflows/triggers.md): The 8 triggers that start a workflow in Default: form submission, incoming webhook, meeting status, website intent signal, CRM record created, CRM record updated, Chrome extension, and API.
- [Action nodes in Default workflows](https://docs.os.default.com/workflows/steps-actions.md): The Send to Webhook, Redirect, Date Transformer, and Create Variable nodes in Default workflows: fields, examples, and how later nodes use their results.
- [CRM nodes in Default workflows](https://docs.os.default.com/workflows/steps-crm.md): Create, match, update, and convert Salesforce and HubSpot records, activities, and associations from a Default workflow, with each provider's fields shown separately.
- [Sequencing nodes in Default workflows](https://docs.os.default.com/workflows/steps-sequencing.md): Add a person to a sequence, cadence, campaign, or flow in Apollo, Outreach, Salesloft, Amplemarket, Smartlead, HubSpot, or Gong Engage from a Default workflow.
- [Notification nodes in Default workflows](https://docs.os.default.com/workflows/steps-notifications.md): Send Slack messages, create Slack channels, add channel members, and email your team from a Default workflow.
- [Enrichment nodes in Default workflows](https://docs.os.default.com/workflows/steps-enrichment.md): Enrich people and companies inside a Default workflow with the Enrich Data node, using 1 provider or an enrichment waterfall.
- [Routing and scheduling nodes in Default workflows](https://docs.os.default.com/workflows/steps-routing-scheduling.md): The Round-Robin, Rules of Engagement, Display Scheduler, and Cancel meeting nodes: assign a lead to a queue member, choose an owner with a ruleset, book a meeting in the workflow, or cancel one.
- [Logic and timing nodes in Default workflows](https://docs.os.default.com/workflows/steps-logic-timing.md): The Multi-Branch, Run Experiment, and Time Delay nodes in Default workflows: branch on conditions, split runs by percentage for a test, or pause before the next node.
- [AI nodes in Default workflows](https://docs.os.default.com/workflows/steps-ai.md): Use the AI Prompt node to send workflow data and instructions to a large language model from a Default workflow, then use the response in later nodes.
- [Deep Research node in Default workflows](https://docs.os.default.com/workflows/steps-research.md): The Deep Research node, in beta, sends a research agent powered by Parallel to the live web from a Default workflow and returns structured, typed fields.
- [Workflow run logs in Default](https://docs.os.default.com/workflows/run-logs.md): Review every run of a Default workflow: what triggered it, the path it took, what each node read and wrote, and why any node succeeded, warned, or failed.
- [Website form capture in Default](https://docs.os.default.com/forms.md): How Forms in Default captures submissions from the forms already on your website with the Pixel, identifies the visitors behind them, and starts workflows from each submission.
- [Website tracking domains in Default](https://docs.os.default.com/forms/signals.md): How to connect the websites the Default Pixel tracks in Signals, and manage their subdomains, status, discovered paths, Reveal, and form catalog mode.
- [Install the Default Pixel](https://docs.os.default.com/settings/pixel.md): How to install the Default Pixel on your website: add a domain in Signals, copy the snippet, place it in every page's head, check that events arrive, and control what it captures.
- [Manage captured website forms in Default](https://docs.os.default.com/forms/your-forms.md): How to add the forms on your website to Default with Catalog forms or create them in Default, map their fields to Person and Company records, review field changes, and start workflows from submissions.
- [How Default books a meeting from a form submission](https://docs.os.default.com/forms/scheduler.md): How Default turns a website form submission into a booked meeting: the Pixel captures the form, the Form Submission trigger starts a workflow, routing picks the host, the Display Scheduler opens a calendar on the same page, and the workflow follows up when the visitor doesn't book.
- [Adding a scheduler to HubSpot forms in Default](https://docs.os.default.com/forms/hubspot.md): Show a Default booking calendar after a visitor submits an embedded HubSpot form: the HubSpot embeds the Pixel supports, how it detects them, field mapping for HubSpot property names, the HubSpot setting to change, and troubleshooting.
- [Adding a scheduler to Marketo forms in Default](https://docs.os.default.com/forms/marketo.md): Show a Default booking calendar after a visitor submits an embedded Marketo form: how the Pixel detects Marketo Forms 2.0 forms, how it skips the Marketo follow-up page, field mapping, and troubleshooting.
- [Adding a scheduler to Pardot forms in Default](https://docs.os.default.com/forms/pardot.md): Show a Default booking calendar after a visitor submits a Pardot (Marketing Cloud Account Engagement) form: how the Pixel recognizes Pardot forms, why their submissions go through the Forms SDK, the setup steps, and troubleshooting.
- [Website visitor identification in Default](https://docs.os.default.com/forms/reveal.md): How Reveal in Default identifies the companies and people that visit your website, with the Account Signal and People Signal triggers that start workflows when it does.
- [Pixel privacy and consent in Default](https://docs.os.default.com/forms/privacy.md): What the Default Pixel never captures, the pages and forms it skips, how to turn capture off, and how analytics and marketing consent gate tracking and Reveal.
- [Cookies and browser storage in Default](https://docs.os.default.com/forms/cookies.md): Every cookie and browser storage item the Default Pixel and scheduler use, which product part each one belongs to, which ones are strictly necessary and why, and how to set up your consent banner.
- [Troubleshoot website form capture in Default](https://docs.os.default.com/forms/troubleshooting.md): Fixes for common Forms and Pixel problems in Default: a domain stuck on Inactive, form submissions that don't show up, and getting the install script again.
- [Set up the Default Pixel and Forms SDK](https://docs.os.default.com/pixel-sdk-setup.md): Step-by-step setup for the Default Pixel and Forms SDK: connect a domain, add and map your form, install the SDK, and verify a submission and its workflow.
- [Forms SDK best practices for Default](https://docs.os.default.com/pixel-sdk-best-practices.md): Best practices for the Default Forms SDK: initialize early, start pre-enrichment before submission, handle every workflow result, and secure scheduler messages.
- [How the Default Pixel and Forms SDK work](https://docs.os.default.com/pixel-sdk-integration-guide.md): How the Default Pixel and Forms SDK handle visitor identity, form submissions, pre-enrichment, workflows, and scheduler handoffs, from page load to booked meeting.
- [Default Pixel and Forms SDK API reference](https://docs.os.default.com/pixel-sdk-reference.md): Reference for every configuration option, method, return value, and scheduler event in the Default Pixel (index.js) and Forms SDK (sdk.js), with defaults.
- [Default MCP server](https://docs.os.default.com/mcp-server.md): Connect Claude, Cursor, Codex, VS Code, or another MCP-compatible AI client to your Default workspace with the Default MCP server (beta): setup, tools, access, and troubleshooting.
- [Chrome extension in Default](https://docs.os.default.com/chrome-extension.md): Use the Default Chrome extension to pick up a lead on a Gmail, Salesforce or HubSpot page, look it up, request enrichment, route and book it through a workflow, and reassign, reschedule or mark no-shows on upcoming meetings.
- [Settings in Default](https://docs.os.default.com/settings.md): What you can configure in Default Settings: your profile, calendar and notifications, plus workspace users, branding, integrations, notification domains, webhooks, and SSO.
- [Your user profile in Default](https://docs.os.default.com/settings/profile.md): How to edit your Default user profile: name, profile picture, display name, scheduling username, job title, phone number, and your personal integration mappings.
- [Your calendar and availability in Default](https://docs.os.default.com/settings/availability.md): How My Calendar in Default controls when you can be booked: meeting buffers, notice period, vacation mode, your primary calendar, work hours, and out-of-office time.
- [Work hours and schedules in Default](https://docs.os.default.com/settings/availability/working-hours.md): How to create named work schedules in Default that set the days, hours, and timezone you're open for bookings, and choose the primary schedule Default uses for your open slots.
- [Out-of-office blocks in Default](https://docs.os.default.com/settings/availability/ooo.md): How to add, edit, and delete out-of-office (OOO) blocks in Default so no one can book you during that time, and how calendar-synced OOO and routing policies use them.
- [Your notification settings in Default](https://docs.os.default.com/settings/notifications.md): How to choose which meeting, routing, and general events Default notifies you about, and on which channels: Slack, email, or SMS.
- [Manage workspace users in Default](https://docs.os.default.com/settings/users.md): How admins manage Default workspace members on the Users page: invitations, roles, integration mappings, conferencing, bulk actions, and each member's profile, calendar, and notifications.
- [Workspace notification defaults in Default](https://docs.os.default.com/settings/workspace-notifications.md): How admins set org-wide notification defaults in Default: which channels the workspace allows, default on or off states per type, and the Slack channels that meeting and error notifications post to.
- [Custom email sending domains in Default](https://docs.os.default.com/settings/notification-domains.md): How to add and verify your own email domain in Default with DNS records, so meeting emails can send from the host's inbox address or a custom address instead of Default's shared sending domain.
- [Branding in Default](https://docs.os.default.com/branding.md): How admins manage all Default branding on one page: workspace identity, the look of public booking pages, and the style of meeting emails.
- [Booking page appearance in Default](https://docs.os.default.com/settings/scheduler.md): How admins theme public booking pages in Default: presets, background, text and button colors, fonts, logo, the Powered by Default footer, and publishing changes live.
- [Data Model in Default](https://docs.os.default.com/settings/configurations.md): How the Data Model in Default sets up the fields on Person and Company records, the data sources that fill them, and the enrichment waterfalls that workflows use.
- [Person and Company fields in Default](https://docs.os.default.com/settings/configurations/objects.md): How to manage the fields on Person and Company records in Default's Data Model, and set the priority order of the data sources, such as your CRM, that fill each field.
- [Enrichment waterfalls in Default](https://docs.os.default.com/settings/configurations/waterfalls.md): How enrichment waterfalls in Default combine up to 5 providers (Clearbit, Apollo, People Data Labs, and Wiza) in priority order, how each surface runs them, and how credits are billed.
- [Integrations in Default](https://docs.os.default.com/settings/integrations.md): The tools Default connects to: Salesforce and HubSpot, sequencing tools, Slack, Default-managed enrichment and website intent providers, calendars, and conferencing, with who can connect each.
- [Default and Salesforce: what syncs, what triggers, which permissions](https://docs.os.default.com/settings/integrations/salesforce.md): See what Default reads from and writes to Salesforce, which objects start workflows, how Data sync and Watched fields work, and which package, permissions, and user mappings the connection needs.
- [Default and HubSpot: what syncs and what triggers](https://docs.os.default.com/settings/integrations/hubspot.md): See what Default reads from and writes to HubSpot, which objects start workflows, how Data sync and Watched fields work, what connecting needs, and how Default users map to HubSpot owners.
- [Running Default with Salesforce and HubSpot at the same time](https://docs.os.default.com/settings/integrations/salesforce-and-hubspot.md): Default can connect Salesforce and HubSpot at the same time, and this page explains how workflows, routing, user mappings, Data sync, and the Chrome extension choose a CRM when a team uses both.
- [Google Calendar integration for Default](https://docs.os.default.com/settings/integrations/google-calendar.md): How each member connects Google Calendar to Default so Default can check their availability and add meetings booked through Default to their calendar.
- [Outlook Calendar integration for Default](https://docs.os.default.com/settings/integrations/outlook.md): How each member connects Outlook Calendar to Default so Default can check their availability and add meetings booked through Default to their calendar.
- [Zoom integration for Default](https://docs.os.default.com/settings/integrations/zoom.md): How an admin connects Zoom to Default once for the whole workspace, so events can use Zoom or Zoom Personal as their location and booked meetings get Zoom links.
- [Google Meet integration for Default](https://docs.os.default.com/settings/integrations/google-meet.md): How Default adds Google Meet links to booked meetings through each member's Google Calendar connection, with the Calendar Default event location and the Conferencing Setup preference.
- [Microsoft Teams integration for Default](https://docs.os.default.com/settings/integrations/microsoft-teams.md): How Default adds Microsoft Teams links to booked meetings through each member's Outlook Calendar connection, with the Calendar Default event location and the Conferencing Setup preference.
- [Apollo integration for Default](https://docs.os.default.com/settings/integrations/apollo.md): How Default works with Apollo: connect Apollo.io (Sequencing) with your API key to add contacts to sequences from workflows, and use Default-managed Apollo.io (Enrichment) in waterfalls.
- [Outreach integration for Default](https://docs.os.default.com/settings/integrations/outreach.md): How to connect Outreach to Default so workflows can add prospects to Outreach sequences with the Add to Outreach Sequence node.
- [Amplemarket integration for Default](https://docs.os.default.com/settings/integrations/amplemarket.md): How to connect Amplemarket to Default with an API key so workflows can add leads to Amplemarket sequences with the Add to Amplemarket Sequence node.
- [Salesloft integration for Default](https://docs.os.default.com/settings/integrations/salesloft.md): How to connect Salesloft to Default so workflows can add people to Salesloft cadences with the Add to Salesloft Cadence node.
- [Smartlead integration in Default](https://docs.os.default.com/settings/integrations/smartlead.md): How to connect Smartlead to Default with an API key and add leads to Smartlead campaigns from workflows with the Add to Smartlead Campaign node, including the lead fields Default sends and how it reports skipped leads.
- [Gong Engage integration for Default](https://docs.os.default.com/settings/integrations/gong.md): How to connect Gong Engage to Default so workflows can add contacts to Gong Engage flows, and so bookings can create consent-enabled Gong meetings.
- [Slack integration for Default](https://docs.os.default.com/settings/integrations/slack.md): How to connect Slack to Default so members get Default notifications in Slack and workflows can post messages and create channels.
- [Enrichment providers](https://docs.os.default.com/settings/integrations/enrichment.md): Connect the providers behind enrichment Waterfalls and Website Intent visitor identification.
- [Clearbit enrichment and Clearbit Reveal in Default](https://docs.os.default.com/settings/integrations/clearbit.md): How Default uses Clearbit for person and company enrichment and Clearbit Reveal for real-time company identification of website visitors, who supplies the data, the credits each lookup uses, and how to turn them on.
- [People Data Labs enrichment in Default](https://docs.os.default.com/settings/integrations/people-data-labs.md): How Default uses People Data Labs to enrich people and companies: where it shows up, the inputs it accepts, the fields it returns, the credits each lookup uses, and how to turn it on.
- [Wiza enrichment in Default](https://docs.os.default.com/settings/integrations/wiza.md): How Default uses Wiza to find verified work emails, phone numbers, and profile data from a LinkedIn URL or an email: enrichment levels, credits, fields, and setup.
- [Icypeas email verification in Default](https://docs.os.default.com/settings/integrations/icypeas.md): How Default uses Icypeas to verify email addresses you already have, without finding new ones: where it runs, the fields it returns, the credits it uses, and how to turn it on.
- [Abstract email and IP checks in Default](https://docs.os.default.com/settings/integrations/abstract.md): How Default uses Abstract Email Reputation to check email quality and risk, and Abstract Geolocation to look up location and network details for an IP address: where each runs, fields, credits, and setup.
- [Demandbase website visitor identification in Default](https://docs.os.default.com/settings/integrations/demandbase.md): How Default uses Demandbase to identify the company behind a website visit in real time: how it runs with Reveal and Clearbit Reveal, the fields it returns, when it uses credits, and how to turn it on.
- [Vector website visitor identification in Default](https://docs.os.default.com/settings/integrations/vector.md): How Default uses Vector to identify the people and companies visiting your website in batches: how the Default Pixel loads it, the People Signal trigger, the fields each identification carries, when it uses credits, and how to turn it on or off.
- [Connect Segment, PostHog, Mixpanel, and Amplitude to Default by webhook](https://docs.os.default.com/settings/integrations/product-analytics.md): Segment, PostHog, Mixpanel, and Amplitude connect to Default by webhook, not natively, so product events start workflows through the Incoming Webhook trigger and the Send to Webhook node sends Default data back to them.
- [Connect Hightouch, Census, and Databricks to Default by webhook or API](https://docs.os.default.com/settings/integrations/warehouses.md): Data warehouses and reverse ETL tools such as Hightouch, Census, and Databricks connect to Default by webhook or through the public API, not natively, so each row they send starts a workflow run and the Send to Webhook node sends Default data back out.
- [Connect Customer.io to Default by webhook](https://docs.os.default.com/settings/integrations/customer-io.md): Customer.io connects to Default by webhook, not natively, so Customer.io webhooks start workflows through the Incoming Webhook trigger and the Send to Webhook node updates Customer.io from Default.
- [Connect Zapier to Default by webhook or API](https://docs.os.default.com/settings/integrations/zapier.md): Zapier connects to Default by webhook or through the public API, not natively, so a Zap starts a workflow through the Incoming Webhook or API trigger and a workflow starts a Zap with the Send to Webhook node.
- [Incoming webhook secret in Default](https://docs.os.default.com/settings/webhook-secret.md): How the single bearer secret that authenticates every incoming webhook in a Default workspace works: who can view it, where to copy it, and how admins rotate it.
- [Single sign-on (SSO) in Default](https://docs.os.default.com/settings/enterprise.md): How admins set up single sign-on (SSO) for a Default workspace: verify email domains and connect an identity provider such as Okta or Microsoft Entra through the WorkOS Admin Portal.
- [Route and book meetings with the Default API](https://docs.os.default.com/api/route-and-book.md): Use the Default public API to fire a routing workflow from your server, take the scheduler it returns, and book a meeting on the chosen rep's calendar in 4 requests.
- [Booking meetings with Default through AI agents and the API](https://docs.os.default.com/api/agent-tools.md): How an AI agent or your own server books meetings in Default: the public API, the @defaulthq/ai-tools package for the Vercel AI SDK, and the MCP server (Beta).
- [List triggers](https://docs.os.default.com/api-reference/triggers/list-triggers.md): Lists the API triggers published in your workspace, each with the fields its connected form expects. Use the field list to decide what to collect before [firing the trigger](/api-reference/triggers/fire-a-trigger).
- [Fire a trigger](https://docs.os.default.com/api-reference/triggers/fire-a-trigger.md): Runs the workflow connected to the API trigger with the submitted form responses. Always returns the `executionId`. The `outcome` is what the workflow exited with, discriminated on `outcome.type`. `scheduler` means a meeting should be booked. Pass `outcome.schedulingLinkId` as the event to [`POST /v…
- [List bookable events](https://docs.os.default.com/api-reference/scheduling/list-bookable-events.md): Returns the organization’s active events, newest first, with cursor pagination.
- [Get event details](https://docs.os.default.com/api-reference/scheduling/get-event-details.md): Returns booking configuration for one event, addressed by event id or slug (scheduling link ids and slugs also resolve), including all configured hosts.
- [Get available slots](https://docs.os.default.com/api-reference/scheduling/get-available-slots.md): Returns bookable start times in [start, end) for the event. The range must end after it starts and may span up to 63 days, nine weeks from whatever start you choose, about two months of availability per request. Page further ranges with the same reservationId. When no reservationId is supplied a new…
- [Book a meeting](https://docs.os.default.com/api-reference/scheduling/book-a-meeting.md): Books a slot previously returned by [`POST /v1/scheduling/events/{event}/slots`](/api-reference/scheduling/get-available-slots), consuming its reservation. The startTime must be a time the event hosts are available for — on SLOT_TAKEN the reservation stays usable, so fetch slots again and retry with…
- [Get a meeting](https://docs.os.default.com/api-reference/scheduling/get-a-meeting.md): Returns the meeting, including its current status, scheduled time, and conference join link.
- [Reschedule a meeting](https://docs.os.default.com/api-reference/scheduling/reschedule-a-meeting.md): Moves the meeting to a new start time, keeping its host assignments.
- [Cancel a meeting](https://docs.os.default.com/api-reference/scheduling/cancel-a-meeting.md): Requires the `scheduling:write` scope.
- [Get available slots for rescheduling](https://docs.os.default.com/api-reference/scheduling/get-available-slots-for-rescheduling.md): Returns available start times in [start, end) for an existing meeting, computed for the hosts already assigned to it. No reservation is created or required. Pass a returned time to [`PATCH /v1/scheduling/meetings/{meetingId}`](/api-reference/scheduling/reschedule-a-meeting). start and end are query…

## OpenAPI Specs

- [openapi](/api-reference/openapi.json)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.