Final Step "Hands-on Exercise: Webhook-Driven Order Processing System"

n8n Academy N8N102: Integrations: APIs and Connected Workflows
1

Hello Team,

As soon as you make this adjustment, you can no longer successfully complete Step 1 in the validation, because “Valid order returns 200 with correct response” always “failed”:

Update RespondSuccess to include full pipeline confirmation:

{
  "status": "processed",
  "order_id": "{{ $('ExecuteProcessOrder').item.json.order_id }}",
  "message": "Order processed successfully",
  "stored": {{ $('ExecuteProcessOrder').item.json.stored }},
  "stored_order": {{ $('ExecuteProcessOrder').item.json.stored_order }},
  "processed": true,
  "processing_result": "{{ $('ExecuteProcessOrder').item.json.processing_result }}"
}

The problem is in “status”: “processed” — previously “status”: “accepted” — if you change it to “accepted” the validation works and you get the confirmation code at the end.

Best regards — Michael

2

The validation webhook checks for the exact response shape it was built to expect, including status: "accepted". Changing to "processed" fails the validator assertion even though the logic is right.

Cleanest fix: keep status: "accepted" in the RespondSuccess node for the validation step, but add your extra pipeline fields alongside it so both the validator and your workflow are happy:

{
  "status": "accepted",
  "order_id": "{{ $('ExecuteProcessOrder').item.json.order_id }}",
  "message": "Order processed successfully",
  "stored": {{ $('ExecuteProcessOrder').item.json.stored }},
  "processed": true,
  "processing_result": "{{ $('ExecuteProcessOrder').item.json.processing_result }}"
}

The course instruction to change to "processed" looks like a doc inconsistency - the validation endpoint still expects "accepted". Keep the original status field and Step 1 will pass while the extra fields still appear in the response.

3

This solution works. Thanks

4

Thanks, course text updated.