What are action integrations?
Compared to data integrations, establishing action integrations does not lead to content being synched into the Zive Search Index. Meaning content does not become part of your company knowledge on the platform, but instead you allow users to work with the integrated systems by executing targeted actions.
Tip: To understand action integrations from a user perspective take a look at our user guides for integrations in
Establishing action integrations
Available integrations
To activate action integrations navigate to the platform administration via your profile in the bottom left corner. When you visit Integrations data integrations are displayed by default and you can switch to the Actions tab.
Here you find an overview of all integrations that we currently support for actions:
Note: We are continuously expanding our integrations catalog. If you miss a relevant system, please reach out to [email protected].
Integration | Type |
Airtable | Direct integration |
Asana | MCP |
Atlassian | MCP |
Github | MCP |
Gmail | Direct integration |
Google BigQuery | Direct integration |
Google Calendar | Direct integration |
Linear | MCP |
Microsoft Planner | Direct integration |
Microsoft Teams | Direct integration |
Outlook Calendar | Direct integration |
Outlook Email | Direct integration |
Salesforce | Direct integration |
Connecting integrations
For most of the available integrations all you need to do is to click on the button "Connect" and authorize the connection. Depending on the system, connecting might require specific roles in the respective systems. This applies especially for direct integrations.
For the following integrations you need to take care of certain preparation in the system first, before being able to connect:
Salesforce
Note: If you want to connect to these systems specifically, please reach out to us at [email protected] for specific instructions.
Connecting custom MCP server
Besides the integrations provided by us you always have the possibility to add custom MCP servers to connect to any system. In order to do so, simply click on the button "Add MCP server" and provide the required details about the server in the form that opens.
Note: If you need technical support on how to set up a custom MCP, reach out to [email protected].
Configuring action integrations
After successfully connecting an integration you can precisely configure which actions should be available to users to which degree.
Configure availability in agents and/or chat
For connecting systems you can click on the "Setup" button to see all actions that are supported via the integration.
You can first decide whether an action should be
only available in Zive Agents,
only in the Zive Chat,
or both.
There might be very specific actions that you don't want to have all users access to via the Chat, but instead to only use them in agents that handle very specific tasks or use cases.
Configure degree of availability in the chat
For the Zive Chat specifically you can define exactly when this action should be available and choose between the following four options:
Always on: The action is permanently available in the Zive Chat and does not require any specific settings or a mentioning by the user.
On demand: The action only becomes available if the user explicitly mentions the integration by typing "@" in the chat and selecting it.
In company context: The action can only be used by the Zive Chat if the AI nudge to search the company knowledge is activated.
In web context: The action can only be used by the Zive Chat if the AI nudge to search the web is activated.
Tips:
For most actions you activate in the Zive Chat the first two options ("always on" and "on demand") are most relevant.
Even if configured to "always on", we recommend users to always use the mentioning to support the models decision.
Configure whether actions should run automatically
Lastly you can configure for each action whether the it should be performed immediately or request a confirmation by the user first. This setting affects the Zive Chat primarily. For agents this can be overwritten in the agent settings.
Generally auto-run provides a faster experience, while manual approval is more secure.
Tip: As a best practice we frequently see the following selection for the auto-run setting
Auto-run: Actions that retrieve/fetch data, e.g. fetch email content, list meetings, ...
No auto-run: Actions that edit/update data, e.g. sending messages, creating tasks, ...
Security aspects of action integrations
All integrations we provide require a user authentication in addition to the general connection in the administration. Through this user identification we secure that each user can only perform actions based on their access and permissions in the respective system.
When connecting a custom MCP server, user authentication is not required. This means it's possible to connect systems, e.g. via a technical account and allow users to perform actions via Zive without authenticating themselves in the system directly. When you do this you should consider potential risks, e.g in regards to the logging changes and permission enforcement.