> For the complete documentation index, see [llms.txt](https://docs.akkio.com/akkio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akkio.com/akkio-docs/integrations/zapier.md).
# Zapier
#### **Building your Zapier Zap**
Log into Zapier and start a new workflow. Because we will monitor Twitter, we will begin with the Twitter integration and connect it to our account. Because I don’t run a restaurant, we will use my Twitter handle @jonathonreilly. We will search for when my account is mentioned:
And we will trigger on my handle.
You can then quickly confirm that the trigger is working correctly by validating that it pulls your latest mention. The next step is to pass the mentions (reviews) to the Akkio model we set up in Step 1. Add a step, search Akkio, and connect it. Then choose the event “make a prediction,” as shown below:
Next, you will need to connect your Akkio account. You only need to do this step once. After that, all your deployed ML models will be available in Zapier. Follow the link to your team settings page in the Akkio web app, copy and paste your API key, then choose to continue.
Now that your Akkio account is connected to Zapier, you can continue with the deployment or exit. Please look at the Zapier Deployment Page for more details and testing options.
---
# 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.akkio.com/akkio-docs/integrations/zapier.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.
