Connecting Your Integrations

The current V2 web Settings page exposes organization Stripe onboarding, a shared SMS sending number, and, for members with the manage integrations permission, a Settings > Integrations hub with the External API keys page, the Zapier / Make Webhooks page, the Lead Connectors page, the Google Lead Ads page, the Meta Lead Ads page, and the Workiz page. Those V1 administration surfaces remain required parity; deployment-managed integrations can still exist without implying that their V1 setup UI is present in V2.

Current V2: External API Keys

1. Open Settings in the Business section of the sidebar.
2. Select Open Integrations in the Integrations section, then Set up on the External API card.
3. On the Create key tab, name the key, choose Live or Test, pick the scopes the integration needs, and optionally set a rate limit and expiry.
4. Copy the raw key from the green banner. It is shown once; afterwards only the prefix is visible.
5. Use the Keys tab to edit scopes, limits, and expiry or to revoke a key, and the Request logs tab to review recent calls per key.

Test keys read and write isolated sandbox records for leads, clients, and estimates, so an integration can be exercised without touching live data. Sandbox estimate writes are allowed even though live estimate writes are not available in V2 yet. See Auth and Scopes and the External API Overview for the request contract and what is live in V2 today.

Current V2: Outgoing Webhooks

1. Open Settings, then Open Integrations, then Set up on the Zapier / Make Webhooks card (you need access to every location).
2. Select Add webhook, name the endpoint, paste its HTTPS URL, and check the events it should receive.
3. Copy the signing secret from the green banner; it is shown once.
4. Use Test on the card to send a sample delivery, and watch Recent deliveries for the result.

See Webhook Integrations for the event catalog and payloads and Webhook Signing for verification.

Current V2: Lead Connectors

1. Open Settings, then Open Integrations, then Set up on the Lead Connectors card (you need access to every location).
2. Select Add connector, name it, choose the provider (API, Website form, or Email forward), and leave it on Draft.
3. Add a source label, an assigned rep, a notes prefix, and field aliases for the source's own field names, then select Create connector.
4. Use Run Test Import on the card with a sample payload, then Activate.
5. Point the source at the card's connector key (API), public endpoint (website form), or forwarding address (email), and watch Recent Imports and the Review Queue.

See Lead Connectors for field mapping, the review queue, and each connector type's setup.

Current V2: Google Lead Ads

1. Open Settings, then Open Integrations, then Set up on the Google Lead Ads card (you need access to every location).
2. Leave Form ID blank unless one Google form should be the only one to import, enter a Lead Source Label that matches an active lead source name if the leads should carry a source (a label that names no active source leaves the lead without one), and click Enable Google Lead Ads.
3. Copy the Webhook URL and the Google Key into the lead form webhook settings in Google Ads, run Google's webhook test, and submit one real lead.
4. Watch Recent imports on the page: Google's test shows as Ignored, a complete first-time lead as Imported, a repeat of the same Google lead id as Replayed, and a lead missing a name, a contact method, or a service address as Review required (complete it in the Lead Connectors Review Queue).

See Google Lead Ads for the field mapping and the key-only versus key-plus-form choice.

Current V2: Meta Lead Ads

1. Open Settings, then Open Integrations, then Set up on the Meta Lead Ads card (you need access to every location). If the card says Needs Env, a platform admin still has to configure the shared Meta app.
2. Click Connect Meta, approve the Meta login, and click Use This Page if the login manages more than one page.
3. Wait for the success state, then submit one real lead form on the page.
4. Watch Recent imports on the page: a complete lead shows as Imported, a repeat of the same Meta lead as Replayed, and a lead missing a name, a contact method, or a service address as Review required.

See Meta Lead Ads for the optional settings, the field mapping, and reconnecting.

Current V2: Workiz

1. Open Settings, then Open Integrations, then Set up on the Workiz card (you need access to every location).
2. On the Connection tab, paste the Workiz API token and API secret and click Connect Workiz. CE Pro checks them against Workiz and creates the workspace's Workiz lead connector.
3. Copy the endpoint and the signing secret into a Workiz webhook that posts lead and job events, then choose the sync switches and click Save Sync Settings.
4. On the Migration tab, Preview From Workiz (or paste a CSV export), read the dedupe result, then Import.
5. When the migration is done, the owner clicks Enable Native CRM And Disable Workiz Sync.

See Workiz for the sync switches, the field mapping, the retry queue, and troubleshooting.

Current V2: Stripe Deposits

1. Open Settings in the Business section of the sidebar.
2. Find Payments (Stripe) near the top of the page.
3. Select Set up payments or Resume Stripe onboarding.
4. Complete Stripe's hosted onboarding and return to Clean Estimate.
5. Confirm the card reports that charges are enabled.

Current V2 Stripe collects an accepted proposal's required deposit or full upfront payment and a sent invoice's exact ledger-derived balance. Office keyed-card entry, tips, offline payment recording, refunds/credits, and mobile invoice collection remain parity work.

For the full current procedure and preserved V1 collection boundary, see Connecting Stripe.

Current V2: SMS Sending Number

1. Open Settings.
2. Find Texting (SMS).
3. Save the workspace number in E.164 format, such as +17177440798.

Without a configured number, V2 refuses outbound SMS instead of borrowing a sender shared with another company. Telecom provider credentials and number provisioning remain deployment-managed. Teammates with manage_phones configure the current Twilio forwarding, voicemail, retention, and signed inbound webhook under Settings > Company calls, recording, and voicemail; V2 still does not expose a legacy Phone / Voice credential card.

V1 Integration Catalog Reference

The procedures below describe V1 administration and are not current V2 Settings routes:

• Esendex or Twilio: configure SMS and voice provider credentials, forwarding, and shared-number behavior from the V1 Phone / Voice controls.

Use the linked versioned guides when supporting the V1 application: Esendex. Restoring their useful administration in V2 remains parity work. Every card on the V2 Settings > Integrations hub opens a working page today; phone and texting providers are not an integration card in V2 (see the Communications guides for the V2 setup).

Next Steps

• Connect Stripe for Current V2 Proposal Deposits
• Configure the Current V2 Workspace
• Set Up Lead Connectors