# Webhook Integration

**OrcaSheets does support webhooks, but only for data syncing and notifications, not as a generic API for product features. This page is explicit about what exists, what does not, and what you can reliably build on.**

## What webhooks are for (supported)

Webhook integration exists for **data syncing and notifications**.

In practice, this means:

- **Sync data into the OrcaSheets Data Lake** via webhooks, so the data lands where your Projects can use it.
- **Use that synced data** for downstream processing inside the OrcaSheets desktop application.

If your syncing or notification workflow needs custom logic (transforms, validations, routing, custom outputs), we can build **custom Recipes** for you. Custom Recipes are a **custom development** offering, available **only for Enterprise customers**.

Typical downstream uses once data is flowing in:

- **Trigger** your downstream pipelines.
- **Update** your internal status pages.
- **Alert** a team channel.
- **Keep external systems in sync** without polling.

## What webhooks are NOT for

Webhook integration is **not** a general "API surface for OrcaSheets features".

Do not assume OrcaSheets will send you webhooks for individual feature actions like:

- "Pivot Table completed".
- "Dashboard refreshed".
- "Export finished".
- "Join created".
- "Chat response ready".

Those are not the intent of the webhook system, and they are not stable, generally available events.

## Enterprise-only programmatic workflows (custom Recipes)

If you need programmatic workflows beyond syncing and notifications, OrcaSheets offers them **only** as:

- **Custom Recipes**, built as a **custom development** engagement.
- Available **only for Enterprise customers**.

If something of that sort has been built for you, refer to the **deployment-specific documentation** you were provided for:

- Which events exist.
- Payload formats.
- Authentication and signature requirements.
- Retries, ordering, and failure handling.

## What to do instead (when you want "programmatic access")

If your goal is to integrate outputs into other systems:

- **Export** results and integrate downstream: [Exporting Data](/docs/exporting-data).
- **Share via Dashboards** as the main collaboration surface: [Building Dashboards](/docs/building-dashboards).

For the authoritative "what is supported" view, see the [Knowledge Base](/docs/knowledge-base).

## Related pages

- [REST API](/docs/rest-api)
- [JavaScript SDK](/docs/javascript-sdk)
- [Python SDK](/docs/python-sdk)
- [Recipes](/docs/recipes)