> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/readme.md).
# @Human Connections
Overview of the @Human Connections ecosystem
### What are @Human Connections?
Connections is the API Ecosystem for @Human. There are three essential things you need to know:
{% stepper %}
{% step %}
### Open-Source Zapier Alternative
Similarly to Zapier, @Human Connections provides integrations with the API's of an ever-growing ecosystem of third-party technologies - though @Human is all open-source. Enter your API keys and off you go!
{% endstep %}
{% step %}
### Used in @Human Automations
@Human Automations is a TAQ (Trigger/Action/Query) engine in which you use your Connections. For example, you could create an automation where every time a Google Sheet row is added, this triggers the creation of a new record in your CRM.
{% endstep %}
{% step %}
### Easy to Build
API Connections are mostly straightforward for us to build. We just need your suggestions and preferences and we'll do it for free. Interested? Please join @Human Community (top of this page!) and let us know.
{% endstep %}
{% endstepper %}
---
# 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.planetcrust.com/readme.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.
.png?alt=media)