Action / Business automation and AI evaluation
Draft a validated webhook intake Action
Draft webhook intake in Proforma with payload validation, stable event IDs and redacted logs. Prepare synthetic tests before activating any live endpoint.
Integration engineer
Bring this question into Chat
Your starting prompt.
Draft a webhook intake Action for [event schema] using [payload samples]. Validate required fields, distinguish malformed payloads from retried events and use stable event identifiers for deduplication. Document the permitted Source writes and proposed follow-up work, with redacted logs and example failure outcomes. Prepare a test plan using synthetic payloads. Do not activate an endpoint, store real events or trigger external effects before deployment and access review.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
Define inputs, outputs, permissions and failure conditions before implementing an Action. Evaluate AI against representative labeled examples and retain human approval for consequential steps.
For this task, check
The integration owner must validate signature handling, retry semantics and stable event identity before accepting live events.
Before you begin
- Documented event schema and approved Source destination
- Configured Action runtime and secret handling
- Approved production deployment before webhook activation
Repeat execution requires a configured Action. Agree the scope and authority before any external changes or messages.
Synthetic illustrative example
See the method in practice.
Synthetic input. Illustrative output checked locally; this is not a live Proforma run or customer result. Synthetic USD payment events test an intake proposal in memory. This is not a live endpoint or stored payment record.
These invented records explain the method. They are not a recorded Proforma run.
| Event ID | Invoice ID | Amount USD | Currency |
|---|---|---|---|
| E-1 | I-1 | 100 | USD |
| E-1 | I-1 | 100 | USD |
| E-2 | I-2 | -5 | USD |
| E-3 | Missing | 20 | USD |
| Input row | Event ID | Illustrative decision |
|---|---|---|
| 1 | E-1 | Would accept once |
| 2 | E-1 | Would ignore identical retry |
| 3 | E-2 | Reject: amount must be positive |
| 4 | E-3 | Reject: required ID missing |
Method
Require event and invoice IDs, a finite positive amount and USD. For valid events, compare a stable event ID and its payload: an identical retry would be ignored; a conflicting payload rejected. Authentication, signatures and durable deduplication need separate implementation and tests.
What the result tells you
One unique event passes this local validation, one is an identical retry and two are rejected. The intake Action remains proposed and unscheduled; no Source write, webhook activation or external payment effect occurs.
Take the next step
Make it your investigation.
Copy the prompt above, create or open your Workspace, and paste it into Chat. Add the inputs you have permission to use and adapt the assumptions with your agent.
Start exploringYour prompt is carried by copy and paste. Signing up does not submit it or start this work automatically.
Or start with your own agent
The setup prompt includes this public task. Your agent will help you connect when needed and use the access you approve.