> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/integrations/introduction.md).
# Introduction
Browse Zentitle2's native integrations — including FastSpring, Zapier, n8n, HubSpot, Salesforce, Slack, and Stripe — plus the webhooks and APIs you can call directly.
Zentitle2 is designed from the ground up on APIs first, then the UI. Almost any operation that you would like to achieve in licensing can be automated via many means.\
We have built a number of native integrations with CRM and E-commerce vendors, as well as with "workflow automation platforms," which will allow you to connect and set up operations in almost any system.
In addition, our standard web services, webhooks, and APIs can be called directly, and we support OpenAPIs to make that fast and easy.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nalpeiron.com/zentitle2-docs/integrations/introduction.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
