> For the complete documentation index, see [llms.txt](https://www.usemotion.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.usemotion.com/help/settings/integrations/reference-integrations.md). # Reference: Integrations ## Introduction Integrations extend Motion beyond its core app by connecting with the tools you already use. From turning an email or Siri command into a task, to automating workflows with Zapier or APIs, integrations make Motion part of your broader productivity system. This reference explains how each integration works, what data is shared, and the limitations to keep in mind. ### At a Glance * **Native integrations** → Motion supports direct integrations with Email, and Siri for quick task creation and collaboration. * **Task from Email** → Forward emails into Motion to create tasks automatically, with subject, body, and attachments mapped into task details. * **Task from Siri** → Use Siri Shortcuts to add tasks to Motion hands-free with natural voice commands. * **API integrations** → Developers can use Motion’s API to build custom workflows, connect internal tools, or automate large-scale processes. * **Zapier** → Non-technical users can connect Motion with thousands of other apps, automating common workflows like creating tasks from form responses or CRM updates. * **Permissions & security** → Each integration requires specific access (e.g., email forwarding, Siri Shortcuts, API tokens). Motion respects workspace-level permissions and provider rules. * **Limitations** → Some integrations (e.g., Email to Task) support limited field mapping, and API/Zapier usage may be subject to rate limits. --- # 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://www.usemotion.com/help/settings/integrations/reference-integrations.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.