Integrations
Start with Microsoft 365, your AI provider and a CSV of leads. Add enrichment and notification channels when you need them. Each connection below lists what it enables and any setup that requires an administrator or the deployment operator.
This catalog describes implemented workflows, not the connection status of your workspace. Credentials, provider permissions and workflow enrollment must be checked in your workspace before use.
Import selected mailboxes, prepare and send reviewed email, and access permitted calendars.
Microsoft sign-in requires operator setup; advanced app credentials are an alternative. Separate account consent and named shared mailboxes are supported. Microsoft administrator consent and Exchange sending rights may be required. Imports and automation need their own enrollment.
Connect mailboxes → Microsoft 365Use your API key and selected models for drafting, extraction and supported web research.
Model access depends on your account. Set an AI allowance and prepare a sample draft to check access; provider charges apply.
Set AI credentials → AnthropicUse your Bedrock credentials, region and supported model IDs for AI workflows.
Model access depends on your account. Direct Anthropic web research is not supplied through a Bedrock connection.
Set AI credentials → Amazon BedrockMap and import lead files, handle duplicate email addresses, and prepare a reviewed first draft.
Up to 100 leads and 500 KB per file. This is a file import, not continuous synchronization with another CRM.
Import leads → CSV leadsSend supported workspace notifications and event email through your mail server.
SMTP does not import inboxes or replace Microsoft 365 for tracked sales outreach. Test notification delivery after saving.
Set email transport → SMTPSend selected workspace notifications to a channel through its webhook workflow.
Outbound notifications only. Chat history, meeting recordings and transcripts are not imported. Check the channel after a test.
Set notification delivery → Microsoft TeamsResearch companies, discover leads and look up contacts in supported sales workflows.
Enable request limits in Enrichment limits. Your provider plan and credits apply. Manual actions and enabled background jobs can make paid requests; saving a key is not an access check.
Set enrichment key → ApolloLook up contact information while preparing supported sales outreach.
Enable request limits in Enrichment limits. Your provider plan and credits apply. This is contact enrichment, not CRM synchronization; saving a key is not an access check.
Set enrichment key → LushaInstall the configured GitHub App, map repositories to projects and attribute imported pull requests to teammates.
The operator must configure the GitHub App first. Installation permissions and repository mappings determine access; other code and CI providers are not included.
Review GitHub setup → GitHubSend an approved template to an event contact who has explicitly consented.
Requires the supported gateway, workspace credentials and an approved template. This does not provide a WhatsApp inbox or general chat automation.
Review event channels → WhatsApp event follow-upRequest a configured voice follow-up for an event contact who has explicitly consented.
Requires an operator-configured endpoint and workspace credentials. The current adapter accepts Indian +91 mobile numbers only.
Review event channels → Dhwani event callsThe connectors below do not have a supported workspace workflow. No release date is promised. Use CSV for lead imports where appropriate; it does not create ongoing synchronization.
Setup links require a workspace sign-in. Saving credentials does not verify provider access, enable every workflow or guarantee delivery.
Supply workspace credentials or sign in with Microsoft. Choose the mailbox or channel for the workflow.
Run available mailbox checks, prepare an AI draft or send an explicit notification test. Read the limits of each check.
Set your playbook, approval policy, allowance and source settings before enabling background work.
Enable the workflows you need and inspect their delivery or sync history. Recover uncertain attempts from the relevant review screen.
Treat it as unavailable until a supported workflow and its setup path are documented. A provider logo or API alone does not make a working connection.
Custom adapters require engineering work, access design and provider testing. There is no self-service connector builder or generic event-import endpoint.
An operator-managed MCP server exposes selected company tools to compatible clients. It requires a separate deployment and credential setup; it does not connect arbitrary external services.