> 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-handle-opportunities.md). # Integrated Webhooks - Using broadcast to manipulate opportunities ### General concept of broadcast Broadcast in Sprinthub is a signal that can be sent and received at different points of the platform, always related to a lead. In an automation, a broadcast must be emitted (by action) and, at another point, received (as a trigger). Currently, broadcast triggers and actions are available in CRM automations, 360º SAC, chatbots, and automation flows. ## Store funnel - creating stage automation The goal is that when the lead registered on the site completes an order, a broadcast is sent that will be received in the CRM and will trigger a stage automation. This automation has the trigger 'Broadcast received' and the action of changing the opportunity funnel/stage. Upon receiving the webhook signal, the identified lead who has an opportunity in the 'Registered Leads' stage will have their opportunity moved to the 'Active Customers' stage.

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

## Purchase completed webhook As an example, a webhook was created and mapped that expects to receive basic order data, such as the cart containing the products, their prices and names, the buyer's name, their email and WhatsApp. The cart is mapped as a list of objects, allowing, through extra actions, multiple custom objects to be created for the lead, one for each item in the list. The field 'Identifier For' with WhatsApp will be used to identify the lead (if it already exists) on the platform, through their WhatsApp number.

*Webhook Extra Actions - Link custom object.*

*Webhook Extra Actions - Send broadcast.*

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

## Result of the purchase trigger We can check the result of the automations by verifying whether the lead was moved stages, received the message and correctly executed the webhook, through the lead's history.

*Lead history, containing the execution of the webhook, 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-handle-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.