Automate PostgreSQL + Slack
The production database your reports should come from. Team chat where operations actually surface. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Report Assembler already works across PostgreSQL and Slack — free, and it runs on your machine.
Automations teams run
These are not field mappings. An agent reads the PostgreSQL side, works out what it means, and only then decides what — if anything — should happen in Slack.
When a scheduled query runs in PostgreSQL…
…an agent can post a rich channel message in Slack — after reading the context and deciding it should.
When a threshold is crossed in PostgreSQL…
…an agent can DM a teammate in Slack — after reading the context and deciding it should.
When a message hits a channel in Slack…
…an agent can run parameterised queries in PostgreSQL — with the reasoning recorded in the run’s receipt.
When a keyword or mention fires in Slack…
…an agent can write validated rows in PostgreSQL — with the reasoning recorded in the run’s receipt.
When a reaction is added in Slack…
…an agent can produce report extracts in PostgreSQL — with the reasoning recorded in the run’s receipt.
PostgreSQL to Slack, in three nodes
Concretely: a custom-api call to {host}:5432 on one side, the slack-api node on the other, and an agent in between that can decline. Deciding not to write into Slack is a recorded outcome, not a silent one.
{
"id": "07293755-67c6-475e-a75d-efc9f7308b48",
"name": "PostgreSQL → Slack",
"nodes": [
{
"id": "98b0e5b9-3c5a-4e2b-a925-364ecf6d3916",
"text": "Poll PostgreSQL",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"interval": "15",
"unit": "minutes"
},
"description": "Checks PostgreSQL on a schedule.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "255e2ddd-bc04-45b6-ab9e-a3b570e833d4",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the PostgreSQL item. Decide whether it warrants action in Slack, and explain why."
},
"description": "Decides whether this PostgreSQL item warrants anything in Slack.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "b06a2572-5644-49f9-a9bb-7e07e3999246",
"text": "Act in Slack",
"x": 512,
"y": 528,
"isEditing": false,
"type": "slack-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "SEND_MESSAGE"
},
"description": "Interact with Slack to perform various operations such as sending messages, uploading files, managing reactions, and more.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "b291732e-f6d8-4d06-a017-dba47c981548",
"start": {
"id": "98b0e5b9-3c5a-4e2b-a925-364ecf6d3916",
"type": "output"
},
"end": {
"id": "255e2ddd-bc04-45b6-ab9e-a3b570e833d4",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "2af3dff1-36d8-4be5-a7a8-86c6abcdaa76",
"start": {
"id": "255e2ddd-bc04-45b6-ab9e-a3b570e833d4",
"type": "output"
},
"end": {
"id": "b06a2572-5644-49f9-a9bb-7e07e3999246",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Report Assembler
Report Assembler already uses both PostgreSQL and Slack, so installing it gives you this exact hand-off wired up — connected, editable, and running on your own machine.
Runs on your own machine · See what it does
Build it in AGNT
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — PostgreSQL takes a local endpoint on your own machine, Slack takes one OAuth sign-in.
- Build the three nodes above, or start from a marketplace workflow and edit it. The agent in the middle is the part worth spending time on.
- Run it once with an approval gate in place. The receipt tells you what it read, what it concluded, and what it changed in Slack.
PostgreSQL and Slack — common questions
Can I connect PostgreSQL to Slack without writing code?
Yes. PostgreSQL connects with a local endpoint on your own machine and Slack with one OAuth sign-in, both from the local credential vault. You then describe the job in plain language — “when a scheduled query runs, post a rich channel message” — and the agent handles the rest.
How is this different from a field-mapping PostgreSQL to Slack automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Slack, the agent can weigh what arrived from PostgreSQL, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my PostgreSQL and Slack data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: PostgreSQL, Slack, and your chosen model provider — which can be a local one.
What does a PostgreSQL and Slack run leave behind?
A receipt: what was read in PostgreSQL, which tools ran with which arguments, what the agent concluded, and what it wrote to Slack. Anything consequential can sit behind an approval gate so a person signs off before it happens.
