Business administration
Connect and map an external integration
Connect an account and select which of its resources belong to this project.
Before you begin
- Sign in to Eva and select the intended project.
- Use fictional records when practising; changes affect the selected business.
Starting screen: /dashboard/integrations
1. Choose the integration
Open Integrations, review Integration usage, and choose the required category/provider. Built-in EVA CRM and EVA Support remain available separately.
Expected result: The catalogue presents the applicable connection action.
Confirm it worked: Check plan limits before adding an external account.
2. Authorise the correct account
Click the provider’s Connect action and follow its external authorisation instructions. Read account identity and requested consent.
Expected result: After successful provider authorisation, Eva displays the connected account.
Confirm it worked: Never paste provider credentials or tokens into chat, documents or notes.
3. Select a project resource
Open the connection’s settings, use Discover where offered, choose the intended mailbox/business/resource, then Use for project.
Expected result: The selected resource is mapped to the active project.
Confirm it worked: Check resource label and account identity before confirming.
4. Verify the business screen
Open the applicable Inbox, Assets, CRM, Accounting or Support screen. Use View data where offered.
Expected result: Data from the mapped resource is available through Eva’s supported view.
Confirm it worked: Confirm the provider label and record identity.
5. Reconnect or disconnect
Use Reconnect when credentials need renewal. For removal, open the account’s disconnect action, read Disconnect this account?, then choose Cancel or Disconnect.
Expected result: The intended account state changes.
Confirm it worked: Confirm the connection list and affected resource mappings after the action.
Troubleshooting and alternatives
External connection limits do not remove built-in CRM and Support. Provider record availability depends on consent, resource mapping and sync.
Provider setup steps and screenshots vary independently of Eva. Use the provider-specific guides; illustrated provider outcomes in local demos are not evidence of live authorisation.