> 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/integrations-faq.md). # Integrations FAQ #### 1. Will there be native integrations for third-party apps like Notion, ClickUp, Google Sheets, and others? * Currently, there are no plans for native integrations with third-party apps like Notion, ClickUp, or Google Sheets. However, you can still integrate these apps using Zapier or API for seamless task management and automation. #### 2. Can I integrate Motion with Akiflow? * Unfortunately, Akiflow cannot be set as the trigger app, similar to Motion. As a result, Akiflow and Motion cannot be integrated via Zapier. #### **3. Can Motion automatically detect and flag task-like emails for me?** * No, the email must be sent from any email address that’s under your "Accounts” section and forwarded to without any other recipients. * Go to settings * Calendar * Accounts #### **4. Can Motion parse through attachments (e.g., Excel Files, PDFs, Flight Booking Files, etc.)?** * No, Motion cannot read or parse text from attachments or files within the email thread. It focuses solely on the actual email body and its content. Attachments such as Excel files, PDFs, or flight booking files are not processed by Motion for task creation. #### **5. Can I CC, BCC, or add other recipients to the email?** * No, any emails sent to with any other recipients (CC, BCCed or otherwise) would result in failed task creation. #### **6. How long should it take for my tasks to appear?** * Email to task creation is usually swift, and you can expect your tasks to show up in about 30 seconds or less.
--- # 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/integrations-faq.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.