← All integrations
Lead generation integration
Angi for TidyOps
The Angi integration is a company-bound CRM delivery connection that receives supported lead information in TidyOps. Receive Angi leads through a verified, tenant-safe CRM delivery connection.
VerifiedReviewed 2026-09-14
Verified status
TidyOps has confirmed the setup path, production data flow, permission boundaries, known limitations, and support ownership described below.
Setup
- A company owner enters the Angi account ID and a contact email in TidyOps to generate a tenant-specific receiver URL and one-time x-api-key.
- The owner manually emails crmintegrations@angi.com with the requested CRM integration details and completes Angi’s setup and test-lead handoff.
- TidyOps stores only a digest and last four characters of the x-api-key; the clear key is shown only during setup or rotation.
How data moves
- Angi sends the documented fixed JSON lead payload to the tenant receiver using the x-api-key header; no payload company or provider identifier selects a tenant.
- TidyOps validates the fixed schema, normalizes the lead, records consent evidence, and deduplicates by the Angi lead ID for the configured company location.
- Accepted leads are created or updated in the TidyOps acquisition timeline, while delivery status, retry state, and the last delivery are retained for operations.
Limitations
- This is an inbound delivery connection only: TidyOps does not scrape Angi, buy leads, or pull leads through an Angi API.
- The receiver accepts the documented fixed JSON contract and x-api-key authentication only; it does not provide OAuth, arbitrary field mapping, or a general pull/sync API.
- Angi onboarding remains a manual email handoff to crmintegrations@angi.com, and availability depends on Angi accepting and sending the configured test delivery.
Permissions and data access
- Only an authorized company owner or administrator can configure, verify, rotate, revoke, or inspect the Angi connection and its diagnostics.
- The generated credential is tenant-bound and is the only inbound authentication factor; TidyOps never trusts company identity from the JSON payload.
- Lead records, setup state, delivery history, and diagnostics remain company- and location-scoped, with the stored credential represented only by a digest and last four characters.
Support
- TidyOps provides private setup status, test-delivery verification, delivery diagnostics, bounded retry handling, and tenant-specific receiver details.
- Owners can rotate a credential when it is exposed or needs replacement; rotation invalidates the prior key and requires a new Angi handoff.
- Disconnect/revocation invalidates the credential, and TidyOps support can help interpret receiver, validation, retry, and setup errors without requesting the clear key.
Get help
Contact TidyOps about workspace setup or payment records. Contact Stripe about account verification, payouts, or provider availability.