n8n Workflow: Identity Callback Webhook + HTTP Request Test

Test synthetic identity callback handling end-to-end—locally

This n8n workflow creates a synthetic session, waits for an onboarding window, then accepts identity callback events via an HTTP webhook and validates that session state can be recovered and inspected through the local gridzen developer kit fixture service running on 127.0.0.1:8787.

What this workflow does

• Creates a new synthetic session by manually starting the workflow and calling the local fixture service at http://127.0.0.1:8787.
• Simulates an onboarding window by waiting up to 65 seconds using a bounded deadline before recovery is attempted.
• Recovers persisted session state by calling the fixture service recovery endpoint after the wait window completes.
• Receives synthetic identity callback events via an HTTP POST webhook endpoint (the workflow exposes this endpoint for callback delivery).
• Forwards the callback payload to the fixture service so it can apply tenant/user binding and idempotent event handling.
• Responds to the callback sender with the fixture outcome—returning HTTP 200 on success or HTTP 422 with a safe response including “unknown/permission_granted:false” on error.
• Exposes an HTTP GET webhook endpoint to fetch and return the persisted session state from the fixture service for status inspection.

Use cases

• Verify that your identity callback flow correctly updates session state when events arrive within a time window.
• Debug idempotency and tenant/user binding behavior by replaying callback payloads safely.
• Confirm session recovery after a bounded onboarding delay using the fixture service reload endpoint.
• Provide SaaS operators and automation engineers a repeatable local test harness (not cloud-dependent).

Technical details

• Requires self-hosted n8n with access to loopback at http://127.0.0.1:8787 (this does not work from n8n Cloud).
• Pair with gridzen-developer-kit (GitHub repo: immurray/gridzen-developer-kit) and run the Python 3 fixture server per examples/n8n/README.md.
• Uses n8n nodes: manual trigger, wait, webhook, http request, respond to webhook, plus sticky note for workflow clarity.

Setup

Clone https://github.com/immurray/gridzen-developer-kit, start the supplied local fixture server, then copy the generated webhook URLs for /gridzen-fixture-callback (POST) and /gridzen-fi (GET).