Run your workspace

Integrations

Integrations live at /app/integrations. They split into two halves: incoming sources that feed knowledge into the agent, and outgoing destinations that ship leads and events to the rest of your stack.

Incoming sources

Notion and Google Docs share the same workflow: authenticate once over OAuth, pick specific documents in a picker, then ingest the content as knowledge sources. Both support manual re-sync per source rather than continuous polling, so you decide when to refresh. Tokens are encrypted at rest, and disconnecting an integration revokes access immediately.

Slack notifications

Slack receives notifications in three situations:

• A new lead is captured.
• A conversation is routed to a human and needs attention.
• An optional daily summary of conversation activity.

The integration posts under its own name. A built-in test action sends a sample message using the authenticating user's credentials so you can confirm the wiring before live events start firing.

Outgoing webhooks

Webhooks POST to any HTTPS endpoint you control when a lead is captured. Each request is signed with an HMAC header — X-Pitchbar-Signature — so your receiver can verify authenticity. The lead.captured event ships today; conversation events are on the roadmap. Additional event types can be wired in by extending the dispatcher.

CRMs via Zapier

HubSpot and Salesforce don't have native integrations yet. The recommended pattern is to point a webhook at a Zapier catch-hook and let Zapier route the payload into your CRM — that gives you full control over mapping until first-party connectors land.

Access control

Only users with integrations.manage permission — typically Owners and Admins — can modify integrations. Other roles can see which integrations are connected but can't add, remove, or reconfigure them.