> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/integrations/crm-integrations/ygl.md). # YGL The **YFL CRM integration** is by default a one-way sync between Further and YGL, where Further pushes Leads. *** ### CRM Integration Support The **YGL** integration supports: * **Lead Push** * Push leads from Further sources (VSA, phone, web forms, chat) into YGL. *** ### Configuration Options The YGL integration offers flexible configuration options: * **Full Lead Pull & Historical Backfill** * Pull leads out of YGL into Further for inclusion in marketing automation campaigns. * Creates a bidirectional YGL integration * **Webhook Subscriptions per Community** * YGL can send events to Further when certain changes happen; we subscribe at the community level for: * New / updated leads (lead changes). * Task creation. * Tour completion / Post‑Tour. * Move‑in completion. * Lead closed / status changed. * **Push Activities to YGL** * If configured, we can also push SMS activities and phone call transcriptions to YGL --- # 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.talkfurther.com/integrations/crm-integrations/ygl.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.