What You'll Learn
By the end of this article, you'll understand the difference between webhook-triggered and schedule-triggered recipes, how to set up and configure a webhook end-to-end, and which PlanRadar events support webhooks.
What Is a Webhook (and Why Use One)?
A webhook allows PlanRadar to proactively notify your recipe the moment a specific event occurs, rather than your recipe polling PlanRadar on a schedule to check for changes.
Approach | How it works | Best for |
Schedule trigger | Recipe runs at a fixed interval (e.g. every hour) and checks for changes | Batch processing, regular reports, non-time-sensitive workflows |
Webhook trigger | PlanRadar pushes an event to your recipe the instant it happens | Real-time responses, event-driven automation |
Webhook-triggered recipes are more efficient (no unnecessary polling), more responsive (near-instant execution), and consume fewer tasks over time compared to high-frequency schedule triggers doing the same job.
Supported Webhook Events
PlanRadar provides webhooks for a range of events, including:
Ticket created
Ticket updated
User created
Layer created
…
Check the PlanRadar Settings → Account → Webhooks section for the current full list of supported events, as this may expand over time.
Setting Up a Webhook: Step by Step
In PlanRadar Connect
Create a new recipe (or open an existing one).
Choose Workato Webhook as the trigger type.
Follow the guided set-up, it will generate a unique webhook URL for this recipe. Copy it.
In PlanRadar
Navigate to Settings → Account → Webhooks.
Click to create a new webhook.
Select the event you want to trigger on (e.g. Layer Created).
Select the relevant projects this webhook should apply to or leave it empty to apply to all.
Paste the webhook URL from PRC into the Notification URL field.
Save the webhook configuration.
Back in PlanRadar Connect
Trigger the event in PlanRadar (e.g. create a layer in one of the selected projects).
PRC will capture the incoming payload and automatically create the data tree from it.
The webhook trigger step will now expose all fields from the event payload as data pills for use in subsequent steps.
Tip: If you need to recapture the payload (e.g. after PlanRadar adds new fields to a webhook event), simply re-trigger the event from PlanRadar and PRC will update the data tree.
Comments
0 comments
Please sign in to leave a comment.