Integrations
Connect the tools
your team uses.
Connect email, calendars, meetings and prospecting services to Correl. We will confirm which features are available for the accounts and providers you use.
Available connections
What you can connect.
Features vary by provider and setup. Before you switch, we will confirm what each connection supports and which permissions it requires.
| System | Operation & direction | Setup | Availability |
|---|---|---|---|
| Microsoft 365 | Read and update calendars, and configure outbound email through Microsoft Graph. Mailbox synchronisation is assessed separately. | Microsoft account authorisation, the required permissions and service setup. | Confirm the calendar and email features you need. Sending email does not include full mailbox synchronisation. |
| Google Workspace | Create calendar events and configure supported communications with Google Workspace. | Provider authorisation and account configuration. | Confirm the features and sync direction you need. Support differs from Microsoft 365. |
| Zoom, Teams & Meet | Create or add meeting links to calendar invitations, depending on the provider. | Enabled meeting service and relevant account authorisation. | Confirm link creation and invitation behaviour in your evaluation. |
| Prospecting data | Find companies and people, then reveal the contact information you need in Correl. | Prospecting service activation and sufficient Data Credits for paid requests. | Hunter support requires activation. Confirm data coverage and reveal costs for your setup. |
| Email outreach | Prepare email sequences and send follow-ups. Reply handling depends on the connected service. | Connected sending account, audience and sending settings. | Test sending and reply handling before launching outreach. |
Need calling, finance, collaboration or identity connections? Ask us about availability and requirements, including Quirk and Rostra.
Connection setup
Test the connection
before rollout.
Agree what should move between the systems, in which direction and under whose account. Assign someone to manage access and maintain the connection.
Test a small sample first. Check what happens when a request fails, a record already exists or an account is disconnected.
Plan your implementation