AI agent → Postgres

Agents — Claude Code, Cursor, your own app — call a pipeline by id like a named function, authenticated with a per-agent bearer token scoped to an explicit pipeline allowlist. The request body is the event; with ?wait=true the agent gets the post-pipeline payload back to use as a tool result.

how events arrive

1. 01

   create an agent source

   Add an AI-agent source; ingestlayer issues a bearer token bound to an explicit allowlist of pipeline ids the agent may invoke — nothing else.

2. 02

   invoke a pipeline

   From the agent, POST the event payload to https://in.ingestlayer.com/v1/agent/invoke/<pipelineId> with the bearer token. The body is the event; anything goes — the downstream actions handle the shape.

3. 03

   fire-and-forget or wait

   By default the pipeline runs and its destinations fire. Add ?wait=true to also get a poll URL that returns the post-actions payload — the agent reads the enriched, redacted result and uses it as a tool response.

POST /v1/agent/invoke/pl_enrich_lead?wait=true HTTP/1.1
Host: in.ingestlayer.com
Authorization: Bearer ag_live_8fa2…
Content-Type: application/json

{
  "type":  "company.lookup",
  "email": "ada@acme.com"
}

route it to Postgres

Insert each event as a row into a table in your own Postgres.

1. 01

   add the connection

   Paste a Postgres connection string. Connections originate from our EU region — allowlist those egress IPs on your database.

2. 02

   point at a table

   Name the target table. Top-level event fields map to columns, and the full payload is also available as a jsonb column.

3. 03

   map columns

   Match event fields to columns with $event.* references, or accept the default mapping into a typed events table.

INSERT INTO events.signups
  (user_id, email, plan, source, payload)
VALUES
  ('u_018f', 'ada@acme.com', 'pro',
   'marketing-site', '{ … }'::jsonb);

notes

• —The target table must already exist with compatible column types; ingestlayer never runs DDL on your database.
• —Connections come from fixed EU egress IPs — add them to your firewall, or inserts will time out.
• —Use a jsonb column for the full payload when your event shape changes often, so a new field never breaks the insert.

questions

How does an agent send data in?

It calls a pipeline by id like a function: POST the event to /v1/agent/invoke/<pipelineId> with the agent's bearer token. The request body is the event payload.

Can the agent use the processed result?

Yes — invoke with ?wait=true and ingestlayer returns a poll URL holding the post-actions payload (enriched, classified, redacted), so the agent can use it as a tool result. The pipeline's normal destinations still fire.

How do I keep prompt data out of chat?

redact.pii masks sensitive fields per destination, so a warehouse copy can keep the full trace while the Slack message shows only a clean summary.

AI agent, routed elsewhere

• AI agent → SlackSlack
• AI agent → DiscordDiscord
• AI agent → TelegramTelegram
• AI agent → EmailEmail
• AI agent → WebhookWebhook
• AI agent → NotionNotion

other sources, into Postgres

• HTTP webhook → Postgreswebhook.in
• Inbound email → Postgresemail
• everything you can pipe to Postgreshub