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

# Connect non-native apps

> Use webhooks, API requests, and Zapier to connect Cassidy to apps without native integrations.

Cassidy natively integrates with many popular platforms, but you can connect to virtually any app using webhooks, API requests, or [Zapier](/integrations/zapier/overview). This guide walks through each method and when to use it.

## Connection methods

### Webhook trigger

Create a [Workflow](/workflows/overview) with a **Webhook** trigger to receive data from any app that can send HTTP POST requests. When the external app fires an event, it sends a request to your unique Cassidy webhook URL, which kicks off the Workflow automatically.

This is ideal when the external app supports outbound webhooks or notifications. Learn more in the [webhooks guide](/integrations/webhooks).

### Send API Request action

Use the **Send API Request** action inside a [Workflow](/workflows/overview) to push data to any app that has an API. You configure the endpoint, headers, and body directly in the action settings — no code required.

This is ideal when you need Cassidy to write data back to an external system after processing it with AI.

### Zapier

Use [Zapier](/integrations/zapier/overview) as a bridge between Cassidy and 5,000+ apps. You can trigger a Cassidy Workflow from a Zapier automation, or send Cassidy's output to another app through Zapier.

This is ideal when the external app doesn't support webhooks or a direct API, but does have a Zapier integration.

<Tip>You can combine methods. For example, receive data via a webhook trigger, process it with AI actions, then send results to another app using the **Send API Request** action or Zapier.</Tip>

## Store external data in your Knowledge Base

If your goal is to bring external data into Cassidy for your [Agents](/agents/overview) to reference, add a **Save to Knowledge Base** action at the end of your Workflow. This stores the processed data as knowledge that Agents can search and cite.

## Example: connect to ClickUp via Zapier

<Steps>
  <Step title="Create a Zapier automation">
    In Zapier, create a new Zap with **ClickUp** as the trigger app. Choose the event you want to react to — for example, **New Task**.
  </Step>

  <Step title="Add Cassidy as the action">
    Select **Cassidy** as the action app in Zapier. Choose the Cassidy Workflow you want to trigger and map the ClickUp fields to Workflow variables.
  </Step>

  <Step title="Test and activate">
    Run a test to make sure data flows from ClickUp to Cassidy correctly, then turn on the Zap. Every new ClickUp task now triggers your Cassidy Workflow.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Use webhooks" icon="webhook" href="/integrations/webhooks">
    Set up a webhook trigger to receive data from any external system.
  </Card>

  <Card title="Connect via Zapier" icon="question" href="/integrations/zapier/overview">
    Bridge Cassidy with thousands of apps through Zapier.
  </Card>

  <Card title="Build a Workflow" icon="diagram-project" href="/workflows/overview">
    Learn how to create Workflows that process incoming data.
  </Card>

  <Card title="Knowledge Base overview" icon="book" href="/knowledge-base/overview">
    Store external data for your Agents to reference.
  </Card>
</CardGroup>