# Zapier using API

<figure><img src="/files/jthrfQInQguO1M40qK0K" alt=""><figcaption></figcaption></figure>

Zentitle2 supports the use of Zapier by using our standard APIs and Webhooks and as a native integration.

<figure><img src="/files/HDgy4puAQLKvqZ6UyLi8" alt=""><figcaption></figcaption></figure>

All sorts of valuable connections and systems can be set up between these systems.

See our [API docs](/zentitle2-docs/developers/licensing-and-management-apis/api-docs.md) for all the different operations you can build. Above is a simple Slack zap that alerts a Slack channel with activation data. It takes a few minutes to set up.

### What the Zapier Integration / Workflow Automation Enables

* Zentitle 2 supports integration via **its existing APIs and webhooks**, so tools like Zapier (and other workflow automation platforms) can connect to it.
* You can select specific webhook events from Zentitle (e.g., “activation created,” “license expired,” “entitlement changed,” etc.) and have those forwarded through Zapier to downstream systems (e.g., Slack, email, databases, CRMs).
* In a Zapier “Zap,” you typically:
  1. Configure a **“raw hook” trigger** that listens for Zentitle webhook calls.
  2. Parse or transform the webhook’s payload (for example, via a small JavaScript step) to extract relevant fields (eventId, eventCode, payload, etc.).
  3. Use those parsed fields in subsequent Zapier steps to send messages, create records, post to Slack, or trigger other actions in connected apps.
* The documentation shows a simple example: forwarding a Zentitle webhook event into a Slack channel via Zapier—to notify a team about new activations or licensing events.
* While the docs focus on Zapier, the same pattern works with many other workflow/automation platforms, such as Make (Integromat), Integrately, Tray.io, Workato, etc.

***

### Benefits & Value

1. **Low-code / no-code integration**\
   You don’t need to build a custom middleware; using webhooks plus Zapier lets non‐developers build functional automation flows.
2. **Rapid time to set up**\
   The example suggests that once webhooks are configured, you can have a working Zap forwarding events in just a few minutes.
3. **Extensibility & flexibility**\
   Because you’re using APIs + webhooks as the backbone, you can connect Zentitle events to *any* system supported by Zapier (CRMs, Slack, email, databases, ticketing systems, etc.).
4. **Event-driven workflow automation**\
   As licensing or entitlement events occur in Zentitle, you can automatically trigger notifications, data updates, or follow-on processes.
5. **Reusability across tools**\
   The same webhook → Zap flow approach can be reused in different workflow tools. You’re not locked into one vendor.
6. **Better visibility & automation**\
   Teams get real-time updates in their systems (e.g., Slack, CRM) when licensing events happen, which helps with responsiveness, monitoring, and integration consistency.

→ [Learn more](/zentitle2-docs/ui-administration/integrations/zapier-workflow-mgt.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nalpeiron.com/zentitle2-docs/integrations/workflow-management-systems/zapier-native-integrations/zapier-using-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.