DigLab

Use ↓ ↑ to browse results, Enter to open, Esc to close.

Connect integrations and webhooks

Give each connection a defined purpose and test its result.

Outreach DigLab

Reviewed 13 November 2026

Your proposal confirms workspace access, sending accounts, usage and support. A branded login does not connect a mailbox or start a campaign.

Specify the data flow

List the source, destination, fields, workspace and event that should trigger the integration. Open Integrations to inspect supported connections. Keep customer data separate across client projects.

Protect credentials

Use the approved connection method and minimum necessary access. API Keys is an administrator area; never paste a key into documentation, support screenshots or public forms. The existence of API controls does not mean an integration is already connected.

Verify the destination

Test with an agreed sample record and inspect both systems. Check duplicate handling and failure behavior before enabling automatic work. A saved webhook is configuration evidence; a successful destination record proves the action arrived.