> For the complete documentation index, see [llms.txt](https://docs.popl.co/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.popl.co/introduction/integrations/monday-integration/monday-sync-logic.md). # Monday Sync Logic #### Sync Logic When syncing Popl leads to your Monday account, the integration will first perform a read operation to see if the lead already exists. This search (query) uses the lead's **"email"** as a primary key to match any existing lead already in your Monday account. Based on the search, two flows can be taken: **Create New Lead if No Lead Found:** If no lead is found from this initial email search, then the integration will proceed to create a new lead. Lead ownership and any custom mappings will be applied based on the configuration settings described above. **Update Existing Lead If an Existing Lead is Found:** If a lead is found with the Popl lead's specific email, then the integration will proceed to update that lead accordingly instead of creating a new, duplicate lead. *** #### **Need Help?** Contact Popl Support – our team is available to assist at . With 🤍 from Popl. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.popl.co/introduction/integrations/monday-integration/monday-sync-logic.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.