Skip to content
NEWMarketplace and your team: sell what you build, and get plans and changes that are tested before you see them. See what is new

Library / Code, Git & Developer Tools

Code, Git & Developer Tools

Test identity onboarding callbacks and timeout recovery with HTTP Request

Manually runs a synthetic identity session with fixture callbacks and bounded timeout recovery to test an onboarding integration in self-hosted n8n.

What it does

## Test identity callbacks and timeout recovery with HTTP Request Who it is for: developers testing an onboarding integration in self-hosted n8n. How it works: create a synthetic session, receive fixture callbacks, and recover after a bounded wait. The SQLite fixture handles tenant/user binding and idempotent grants. These are simulated outcomes, not real identity verification or signed supplier events. Setup: clone https://github.com/immurray/gridzen-developer-kit and follow examples/n8n/README.md. Start the supplied fixture server in the n8n network namespace at 127.0.0.1:8787. Import this workflow and run Start fixture. Use the documented callback fixtures to test approval, duplicates, wrong bindings and expiry. Requirements: self-hosted n8n and Python 3 with the local fixture service. No provider credentials or paid service is needed. n8n Cloud cannot reach this loopback fixture. Customize: replace the fixture only after implementing authenticated callbacks and your own business rules. Approved never means unconditional customer permission. Keep bounded timeouts and idempotency. Limits: fixture restart persistence tested; n8n Wait resumption after restart not yet tested. This workflow is inactive by default.

The steps

  1. Start fixture
  2. Create fixture session
  3. Wait bounded deadline
  4. Recover existing state
  5. Fixture callback
  6. Apply bound fixture event
  7. Respond with fixture outcome
  8. Read fixture status
  9. Get persisted state
  10. Return persisted state

Similar automations