Salesforce scheduling integration guide
Sync scheduling activity and route by ownership. 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. This page documents the provider workflow. It does not claim that a Salesforce account is connected until authorization and lifecycle tests succeed.
What the Salesforce 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. Sync scheduling activity and route by ownership. A dependable connection must also make authorization, retries, lifecycle changes, and administrator-visible failures understandable.
Salesforce-specific integration decisions
Map leads, contacts, person accounts, companies, opportunities, ownership, required fields, duplicate rules, custom objects, flows, and API limits.
Verify these provider-specific assumptions against current primary documentation, the exact account edition, administrator policy, and a non-production test. Record the required permission, authoritative identifier, fallback state, and owner for reconnects. The Meetin.gs verification standard explains how change-sensitive provider claims are treated.
Salesforce provider review points
- Map leads. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- Person accounts. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- Required fields. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- Duplicate rules. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- Custom objects. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- Api limits. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
Scheduling data and actions in the workflow
The connection should exchange only what the scheduling job requires. For Salesforce, review these three data groups before granting access:
- Contact and company identifiers. Document its source, destination, owner, and behavior after a cancellation or deletion.
- Event type, campaign context, and qualification answers. Document its source, destination, owner, and behavior after a cancellation or deletion.
- Booking, reschedule, cancellation, and outcome state. Document its source, destination, owner, and behavior after a cancellation or deletion.
Common Salesforce scheduling use cases
Routing an account to its existing owner
This use case should be tested from the organizer's action through the guest-facing result. Include a changed meeting and a failed downstream action, not only a successful new booking.
Creating a meeting activity without duplicate contacts
This use case should be tested from the organizer's action through the guest-facing result. Include a changed meeting and a failed downstream action, not only a successful new booking.
Starting a follow-up task when a qualified meeting is booked
This use case should be tested from the organizer's action through the guest-facing result. Include a changed meeting and a failed downstream action, not only a successful new booking.
Salesforce setup and verification checklist
- Document the matching key used for contacts and companies.Record the expected result and the person responsible when it does not occur.
- Test duplicates, missing owners, and an ineligible routing answer.Record the expected result and the person responsible when it does not occur.
- Map lifecycle changes separately instead of treating every event as a new booking.Record the expected result and the person responsible when it does not occur.
Availability, permissions, and limits
CRM automation is only as reliable as ownership and matching data. Define a visible fallback for ambiguous or missing records.
Meetin.gs currently lists this connection as part of its integration architecture. Use the connection request to confirm current production status, supported accounts, scopes, pricing, and rollout timing. This avoids designing a critical workflow around an unverified roadmap item.
Map the Salesforce workflow before connecting it.
Bring the trigger, required data, failure path, and desired guest outcome.
Discuss the connectionSalesforce in one clear flow
Salesforce sends the needed scheduling state to the right system. It keeps the organizer and guest on one record. This prevents a booking change from becoming a silent data mismatch.
Compare this flow with the CRM scheduling integration requirements. Then use the API and webhook help guide to plan retries and recovery.
Simple rule: one booking creates one stable identity. Every later change updates that identity instead of creating a second record.
Salesforce lifecycle acceptance criteria
Use a non-production Salesforce account and one disposable meeting to prove the full connection. Record provider object identifiers beside the Meetin.gs event or booking identifier so every later change can be traced to the same relationship.
| State | Salesforce expectation | Failure to prevent |
|---|---|---|
| Authorization | The intended account grants only the scopes required to associate a meeting with the right person, company, owner, and revenue record so follow-up begins with clean context. | A personal, test, or former employee account silently owns production records. |
| Confirmation | One provider object is created or updated with the required scheduling data. | A retry creates duplicates or exposes fields that the provider does not need. |
| Reschedule | The original Salesforce relationship moves to the new time and preserves identity. | Old and new records both appear active. |
| Cancellation | The provider reaches the documented cancelled, refunded, removed, or inactive state. | The guest receives stale details or capacity remains blocked. |
| Connection failure | The booking stays understandable, the failure is visible, and retry is safe. | A connected action disappears without an owner or participant-facing fallback. |
Provider-specific boundary
Map leads, contacts, person accounts, companies, opportunities, ownership, required fields, duplicate rules, custom objects, flows, and API limits. This is the configuration most likely to distinguish a dependable Salesforce connection from a generic successful API response.
Minimum data review
Confirm the purpose and retention of contact and company identifiers, event type, campaign context, and qualification answers, and booking, reschedule, cancellation, and outcome state. Do not copy free-text responses, calendar descriptions, participant identifiers, or internal links when the stated connection job does not require them.
Salesforce integration questions
Provider-specific answers for teams planning a Salesforce scheduling connection.
Which Salesforce object should a meeting write to?
Decide before you connect: Lead, Contact, Opportunity, or a custom object. Meetings written to the wrong object are difficult to report on and painful to migrate later.
Does a booking create a Lead or update an existing Contact?
That decision belongs to your duplicate-management rules, not the scheduler. Test with an address that already exists in Salesforce and confirm the result is a merge, not a duplicate.
What Salesforce permissions are needed?
Only the object and field access required to write the meeting. Broad API access via an administrator's credentials is convenient and is the most common audit finding.
Before you commit to this connection
Whatever the provider, four checks decide whether a connection is dependable. Test authorization with the identity that will own it in production, one normal confirmation, one reschedule, and one cancellation. Then break it deliberately: revoke access, send a duplicate, and simulate a provider outage.
The meeting must stay visible and manageable even when the connected action fails. Preserve the booking record, show the participant something useful, alert a named owner, and make retry safe. The API and webhook guide covers idempotency and retry design, and the integration directory lists every connection reviewed to the same standard.
A Salesforce operator brief
Map leads, contacts, person accounts, companies, opportunities, ownership, required fields, duplicate rules, custom objects, flows, and API limits.
Routing an account to its existing owner needs a named Salesforce object, authoritative identifier, permitted data set, expected lifecycle result, and recovery owner before it belongs in a production workflow.
Creating a meeting activity without duplicate contacts needs a named Salesforce object, authoritative identifier, permitted data set, expected lifecycle result, and recovery owner before it belongs in a production workflow.
Starting a follow-up task when a qualified meeting is booked needs a named Salesforce object, authoritative identifier, permitted data set, expected lifecycle result, and recovery owner before it belongs in a production workflow.
The operator should be able to trace a guest action from Meetin.gs to the exact provider response and back again. That trace is more useful than a green connection badge because it also explains delayed, duplicated, rejected, and cancelled work.
