Webhooks

term definition characteristics triggers a trigger initiates playbook processes while a playbook can only have one trigger per flow, it can have more than one trigger and/or trigger type turbine currently uses several types of triggers to retrieve and/or ingest data current triggers webhook schedule record event playbook button webhooks are a type of event stream that enables products, vendors, or services to push real time communication into turbine they process and enrich data from third party services and platforms, sending it to turbine records when to use webhooks you want external systems to push events to turbine in real time you want to avoid polling apis for new data you need a simple ingestion method for alerts or events security considerations treat webhook urls as secrets and rotate them if exposed use authentication when possible validate incoming payloads before acting on them key benefits real time data integration webhooks enable seamless real time communication between external platforms and turbine, ensuring that data flows into the system as events happen, reducing the need for polling or manual updates automation with webhook triggers, turbine playbooks can respond instantly to events like system alerts or user actions, streamlining incident response and enhancing workflow automation customizable event handling webhooks can be customized to handle specific events, enabling flexible automation workflows tailored to business needs efficient data processing as webhook events trigger specific playbook actions, turbine can ingest, process, and transform data efficiently, reducing manual workloads and minimizing human error scalability webhooks allow organizations to handle high volumes of event based triggers without requiring constant api calls, improving scalability homepage to access webhooks, follow these steps log in to turbine from the left hand navigation pane, click orchestration and then click webhooks from the webhooks homepage, a list of available (disabled or enabled) webhooks is shown, automatically sorted alphabetically and by playbook if a playbook has more than one webhook, all of the webhooks will display under the playbook's name you can use the features listed in the table to navigate the webhooks homepage for a faster and easier experience feature function filter by name use to filter by webhook name disabled/enabled toggle between the disabled (default) or enabled status ellipsis icon click to edit the webhook in the canvas see docid\ vovv2ts7gzswd0ckgm4no for more information on creating and configuring webhook triggers