Ingress webhook bootstrap

The fastest way to seed a new Lead Pool’s identifier fields is to POST a sample lead via the Ingress webhook. The pool reads the payload, creates any missing fields automatically, and you then rename their labels in the UI.

This is faster than manually clicking through Add-Field in the pool settings, especially for pools with five or more identifier fields.

When to use this

• New Lead Pool, empty schema, no leads yet.
• You want the same firstName / lastName / phone / email keys you use in every other pool (because stable keys make automations portable).
• You’re comfortable making a POST request from Postman, curl, or Make’s HTTP module.

Skip this article and use the UI if the pool’s schema is one-off or you’re not familiar with HTTP tooling.

What you need

Thing	Where to get it
The pool’s Ingress URL	Pool → Settings → Integrations → Ingress webhook
The pool’s Ingress token	Same place, displayed once; copy to a vault
A tool to POST JSON	Postman, curl, Insomnia, Make’s HTTP module — any of these

The token authenticates the call. Pass it as the x-rocketlead-ingress-token request header — not as a query string parameter. (Header names are case-insensitive, but the canonical form in the API schema is lowercase.)

The request

The body has two top-level keys:

• data — an object of Tabellenschema fields keyed by their string key (e.g. firstName). New keys here cause the pool’s schema to grow.
• customFieldData (optional) — an object of Custom Field values keyed by UUID. Validated against the org’s Custom Field registry; unknown UUIDs are rejected.

POST <ingress-url>
Content-Type: application/json
x-rocketlead-ingress-token: <token>

{
    "data": {
        "firstName": "Test",
        "lastName": "Lead",
        "childFirstName": "Kid"
    },
    "customFieldData": {
        "<email-field-uuid>": "test@example.com",
        "<phone-field-uuid>": "+4915112345678"
    }
}

A 200 response returns the created lead. New data keys auto-create Tabellenschema fields on the pool with those raw keys as initial labels. Open the pool in the console — the fields exist, ready for relabeling.

For bootstrap (when no Custom Fields exist yet), use only the data key — every field lands as Tabellenschema and you migrate the generic ones (email, phone) to Custom Fields later.

Pool view is cached for 5 minutes

After the POST, the pool’s column list is cached in the browser for ~5 minutes. Reload the page to see the new columns immediately.

Recommended canonical keys

Stick to a small set of canonical keys across all pools you create. This means automation templates can reference firstName / lastName / phone / email and just work, with no per-pool branching for renamed fields.

Key	Type	Notes
firstName	Tabellenschema, type firstName	Identifier; required for the auto-composed lead name
lastName	Tabellenschema, type lastName	Identifier; same
childFirstName	Tabellenschema, type childFirstName	Optional; martial-arts orgs use this heavily
phone	Custom Field, type phone	Type matters — gives you click-to-call in the lead view
email	Custom Field, type email	Type matters — gives you click-to-mail in the lead view

After the bootstrap

Rename the auto-generated labels (e.g. firstName → “Vorname”) in the pool settings. The key stays stable; only the display label changes. Then assign the appropriate type to each field — see Tabellenschema vs Custom Fields for which fields get which type.

The Ingress webhook isn’t going away — it remains the canonical inbound channel for third-party form fills, Make scenarios, and any custom integration. After bootstrap you’ll keep using it for actual lead intake from external sources.

What’s next

• Move on to Scheduling once the schema looks right.
• Or revisit Tabellenschema vs Custom Fields for the long-term direction.