> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/analyze/integrated-webhooks/integrated-webhooks-common-questions/integrated-webhooks-using-broadcast-to-manage-opportunities.md). # Integrated Webhooks - Using broadcast to manage opportunities In this broadcast use example, a webhook was created that adds to the lead the products they buy in an e-commerce store, through custom objects, and then updates their stage in the CRM. ### General concept of broadcast Broadcast in Sprinthub is a signal that can be sent and received at different points in the platform, always related to a lead. In an automation, a broadcast must be emitted (by an action) and, at another point, received (as a trigger). Currently, broadcast triggers and actions are available in CRM automations, SAC 360°, chatbots, and automation flows. ## Store funnel - creating stage automation The goal is that, when the lead registered on the website completes an order, a broadcast is sent and received in the CRM, triggering a stage automation. This automation uses the event 'Broadcast received' as its trigger and changing the opportunity funnel/stage as its action. Upon receiving the webhook signal, the identified lead, if it has an opportunity in the 'Registered Leads' stage, will have its opportunity moved to the 'Active Customers' stage.

*Configuration of the 'Receive Broadcast - Purchase' stage automation.*

## Completed purchase webhook As an example, a webhook was created and mapped to expect basic order data, such as the cart containing the products, their prices and names, the buying customer's name, and their email and WhatsApp. The cart is mapped as a list of objects, allowing multiple custom objects to be created for the lead through extra actions, one for each item in the list. The 'Identify By' field with WhatsApp will be used to identify the lead (if it already exists) on the platform through its WhatsApp number.

*Webhook Extra Actions - Link custom object.*

*Webhook Extra Actions - Send broadcast.*

## Simulating a purchase trigger As an example, the following trigger will be performed using the Postman software, in the mapped format above.

## Purchase trigger result We can verify the result of the automations by checking whether the lead was moved to a stage, received the message, and correctly executed the webhook, through the lead history.

*Lead history, containing the webhook execution, the broadcast sending*
*and the actions configured in the stage automation.*

--- # 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.sprinthub.com/en/topics/analyze/integrated-webhooks/integrated-webhooks-common-questions/integrated-webhooks-using-broadcast-to-manage-opportunities.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.