> ## Documentation Index
> Fetch the complete documentation index at: https://docs.z360.biz/llms.txt
> Use this file to discover all available pages before exploring further.

# Add and Configure Integrations in Z360

<iframe width="700px" height="400px" src="https://embed.app.guidde.com/playbooks/eGkVJHPZX6iNANrG69fMaT?mode=videoOnly" title="Add Actions And Connect External Integrations In Z360" frameborder="0" referrerpolicy="unsafe-url" allowfullscreen="true" allow="clipboard-write" sandbox="allow-popups allow-popups-to-escape-sandbox allow-scripts allow-forms allow-same-origin allow-presentation" style={{ borderRadius:"10px" }} />

### **Overview**

Integrations in Z360 live in **AI Studio > Actions**. They give Ask Z and AI Studio abilities access to external tools, internal actions, API calls, and custom MCP tools.

The current Actions area supports three main setup paths:

* **Browse Pre-built Integrations** for supported third-party apps.
* **Add Custom Action** for a custom API action you define yourself.
* **Configure MCP** for a custom Model Context Protocol server and its tools.

Use this guide to choose the right integration type and keep connected accounts healthy.

### **Open the Actions Page**

1. Open **AI Studio**.
2. Go to **Actions**.
3. Use **Add Integration** to choose one of the setup options.

The Actions page shows configured action groups and connected integrations as cards. Integration cards can show their connection status, available tools, privacy badge, and quick actions.

### **Browse Pre-Built Integrations**

Use pre-built integrations when Z360 already supports the external app you need.

1. Click **Add Integration**.
2. Choose **Browse Pre-built Integrations**.
3. Review the Popular list first when it is selected by default.
4. Search for the app you want to connect.
5. Filter by category, authentication type, popularity, or status if the list is large.
6. Open the integration and follow the connection steps.

The pre-built integrations browser includes:

* Search
* Popular filter for commonly used business apps
* Category filters
* Authentication filters
* Status filters
* Pagination for larger result sets

If no integrations match your filters, clear the filters and search again.

### **Choose Organization or Private Ownership**

Some credential-based integrations ask for **Ownership**.

| Ownership    | Use it when                                                           |
| ------------ | --------------------------------------------------------------------- |
| Organization | The integration should be available to the team and shared workflows. |
| Private      | The integration should only be available to your user account.        |

Private integrations are marked with a private badge on the action card.

### **Connect Credential-Based Integrations**

For API key, basic auth, or custom OAuth-style integrations, Z360 asks for the required credentials.

1. Choose the integration.
2. Select **Organization** or **Private** ownership.
3. Fill the required credential fields, such as API key, token, client ID, or client secret.
4. Click **Connect**.

Z360 masks sensitive fields such as keys, secrets, passwords, and tokens.

### **Name Connected Accounts**

Some providers do not return a clear account label after connection. When that happens, Z360 asks you to name the connected account.

1. Enter a label such as an email address, workspace name, or account name.
2. If the same label already exists, saving updates the existing connection instead of creating a duplicate.
3. Click **Save**.

Canceling this step discards the connection, and the integration will not be usable until you connect again.

### **Review Integration Cards**

Each configured integration card can show:

* Integration name and icon
* Available actions or tools
* Connection status
* Private ownership badge when applicable
* MCP badge for custom MCP groups
* Edit label controls when supported
* Remove integration or remove MCP configuration actions

Open a card to see the connected account and the available tools. If an integration has no tools, Z360 shows **No tools available for this integration**.

### **Add a Custom Action**

Use a custom action when you need Z360 to call an API endpoint that is not covered by a pre-built integration.

1. Click **Add Integration**.
2. Choose **Add Custom Action**.
3. Name the action clearly.
4. Add a description that explains what the action does.
5. Configure the API endpoint, method, parameters, headers, and authentication details required by the service.
6. Test the action before using it in an ability.
7. Save the action.

Use clear parameter names and descriptions. Ask Z and AI Studio use those descriptions to understand how to fill action inputs.

### **Configure Custom MCP**

Use MCP when you have a server that exposes a set of tools for agents.

1. Click **Add Integration**.
2. Choose **Configure MCP**.
3. Enter the MCP name.
4. Enter the server URL.
5. Choose the supported protocol.
6. Add headers if your MCP server requires authentication.
7. Fetch tools from the server.
8. Save the MCP configuration.

After configuration, the MCP group appears in Actions with an MCP badge. Open it to review available tools or remove the configuration.

### **Use Integrations in Abilities**

Once an integration or action exists, use it from an **Act** node in AI Studio abilities.

Before adding an action to a flow:

* Confirm the integration status is active.
* Confirm the action appears in the available tools list.
* Review the parameter descriptions.
* Test the action with realistic input.
* Use private integrations only for flows that should rely on your account.

### **Troubleshooting**

**I cannot find an app in pre-built integrations**

* Check the Popular filter first, then clear it if you need to browse the full catalog.
* Clear category, authentication, status, and popular filters.
* Search by a shorter app name.
* Use **Add Custom Action** if the app exposes an API but is not listed.
* Use **Configure MCP** if your team has an MCP server for the tool.

**An integration does not appear in an action node**

* Confirm the integration is connected and active.
* Open the integration card and confirm tools are available.
* Reconnect the account if the status is expired or unhealthy.
* Confirm you have access if the integration is private.

**The connected account label is wrong**

* Open the integration card.
* Edit the label when the card allows label editing.
* Use labels that clearly identify the account, workspace, or email address.

**A custom action fails during testing**

* Check the endpoint URL and HTTP method.
* Confirm required headers and credentials are present.
* Confirm parameter names match the external API.
* Check whether the external service requires a specific content type or auth format.

### **Best Practices**

* Use pre-built integrations when available.
* Use organization ownership for shared team workflows.
* Use private ownership for personal accounts or sensitive user-specific tools.
* Keep action names and descriptions specific.
* Test every custom action before adding it to a live ability.
* Remove integrations and MCP configurations that are no longer used.