You don't need to know whether what you're describing calls for a webhook, an AD endpoint, or a plain Nextworld REST API call. Describe the outcome you want, and Ed the Builder figures out the right approach and confirms it with you. For example, you could say "Create a webhook that receives shipment notifications from Acme Freight." Ed the Builder asks clarifying questions to confirm the right approach, such as:
- Whether the external system actually supports webhooks.
- What you'll need to configure on the vendor's side.
- Whether a webhook, an AD endpoint, or a plain Nextworld REST API call actually fits the integration you're describing.
A webhook always passes exactly two fields into your project: a JSON field containing the request headers, and a text field containing the raw request body. Parsing that payload , including extracting fields, mapping them to a table, validating the data, happens entirely in the logic block automatically created for your webhook, not in the webhook definition itself.
Viewing the webhook flow
Select a webhook in the Artifacts panel to see a diagram of how it processes requests.
Example prompts
For example, you could prompt Ed the Builder to:
- "I want our shipping provider to notify us the moment an order ships, so we can update the order record automatically."
- "I want to know right away when a customer pays an invoice through Stripe, and have it marked paid without anyone checking."
- "I want new Freshdesk tickets marked urgent to show up in my app automatically."
- "I want our HR system to tell us as soon as a new employee is added, so we can create their record here."
External systems with custom signing or non-JSON requests
Ed the Builder can build webhooks for external systems that sign requests in a nonstandard way, such as Stripe, Slack, and Twilio, or that send data in a format other than JSON, such as form-encoded data or XML. Describe the outcome you want the same way you would for any other webhook. The raw request body reaches the webhook's logic block as text, and the logic block parses it.
Ownership
Webhooks are owned by the project and can only be created and edited within it. You cannot reference webhooks across projects.