Close scheduling integration guide
Schedule and record meetings in sales workflows. The intended connection would associate a meeting with the right person, company, owner, and revenue record so follow-up begins with clean context.
PROVIDER SETUP GUIDE. Documented workflow, not a live Close connection.Close at a glance
| Category | Sales and CRM |
|---|---|
| Status | Provider setup guide |
| Job | Associate a meeting with the right person, company, owner, and revenue record so follow-up begins with clean context |
| Data exchanged | Contact and company identifiers; event type, campaign context, and qualification answers; booking, reschedule, cancellation, and outcome state |
| Related capability | Crm scheduling integration |
What the Close connection is designed to do
For sales and crm workflows, the important job is to associate a meeting with the right person, company, owner, and revenue record so follow-up begins with clean context. Schedule and record meetings in sales workflows. It sits beside the other sales and crm connections and supports the CRM scheduling integration requirements.
Close-specific integration decisions
Specify how Close leads, contacts, opportunities, activities, owners, sequences, and cancellation reversals should respond to each meeting state.
Check these against current Close documentation and your account edition; the verification standard explains how provider claims are reviewed.
Close provider review points
- Specify how close leads
- Cancellation reversals should respond to each meeting state
Scheduling data and actions in the workflow
For Close, these are the data groups the connection exchanges. Record the source, destination, and owner of each before granting access:
- Contact and company identifiers
- Event type, campaign context, and qualification answers
- Booking, reschedule, cancellation, and outcome state
Common Close scheduling use cases
- Routing an account to its existing owner
- Creating a meeting activity without duplicate contacts
- Starting a follow-up task when a qualified meeting is booked
Close setup and verification checklist
- Document the matching key used for contacts and companies.
- Test duplicates, missing owners, and an ineligible routing answer.
- Map lifecycle changes separately instead of treating every event as a new booking.
Availability, permissions, and limits
CRM automation is only as reliable as ownership and matching data. Define a visible fallback for ambiguous or missing records.
Retry and duplicate handling is covered in the API and webhook guide; ask about Close to confirm production status before building on it.
Map the Close workflow before connecting it.
Bring the trigger, required data, failure path, and desired guest outcome.
Discuss the connectionClose integration questions
Provider-specific answers for teams planning a Close scheduling connection.
How does Close handle scheduled meeting activity?
Close is built around a tight call-and-email activity stream. Confirm how a scheduled meeting appears there so it does not become an entry the team scrolls past.
Does Close support automated lead assignment from a booking?
Verify assignment behavior directly, including how existing ownership is respected. Small-team CRMs often assume a simpler ownership model than a routing workflow needs.
What Close API scope is required?
Only what is needed to create the activity and read the lead. Close API keys are commonly issued per user, so record whose key is in production and how it will be rotated.
Close data and lifecycle decisions
1. Choose the identity model
Close organises work around leads, with contacts, opportunities, and activities beneath them. A booking usually attaches to a contact under an existing lead; decide what happens when no lead matches.
2. Protect business ownership
Lead ownership and sequences matter. A booking should pause an outreach sequence rather than let a scheduled email land after the meeting was confirmed, and it should respect the lead's existing owner.
3. Map the full lifecycle
Create one meeting activity on confirmation, update it on reschedule, and record the cancellation with its reason. Do not create a new activity for every change.
4. Keep traceable evidence
Store the Close activity ID and lead ID with the booking. Test a lead in an active sequence, a merged lead, and a cancelled booking that should reverse a status change.
