// Template · DevOps

Pipeline Alerting with Chat

A reusable alerting pattern for Apache Hop pipelines. Any pipeline can build a message and send it to Slack, Teams, or Google Chat via a WorkflowExecutor — no custom code, no third-party integrations, just the Putki Chat action.

Uses

Chat

Odoo Input

DevOps Alerting Monitoring 8 transforms + 1 workflow Apache Hop

Download .zip

Apache Hop pipeline
Created Jan 23, 2026
Putki 2026.03+

Pipeline

Putki

read-overdue-invoices

OdooInput

get-days-threshold

GetVariable

calculate-days-overdue

ScriptValueMod

filter-by-threshold

FilterRows

sort-by-days-overdue

SortRows

format-message-line

ScriptValueMod

build-summary-message

MemoryGroupBy

chat-slack-notifications.hwf

WorkflowExecutor

Workflow — chat-slack-notifications.hwf

Start

Special

Putki

Send Chat message

ChatAction

Intentionally minimal — Start → Chat. Receives CHAT_MESSAGE and CHAT_WEBHOOK_URL as parameters from the pipeline and sends the message. Reuse it across any pipeline that needs to alert.

How it works

This template shows the standard Putki pattern for sending chat alerts from any pipeline. The pipeline does the work — reading data, computing results, building the message. A single reusable workflow handles the delivery. Change the source, keep the pattern.

The example included here alerts on overdue Odoo invoices — but the same pattern works for any pipeline: failed jobs, low stock, SLA breaches, daily summaries, or anything your data tells you.

Your pipeline builds the message

Any pipeline can produce a chat alert. In this example the pipeline reads overdue invoices from Odoo, computes days overdue, filters by threshold, and assembles one text message with a summary and line-by-line detail.

WorkflowExecutor hands off to the workflow

At the end of the pipeline, a WorkflowExecutor transform calls chat-slack-notifications.hwf and passes the message as a parameter. This keeps delivery logic separate from data logic — the workflow is reusable across any pipeline.

Chat action sends to your channel

The workflow has two actions: Start and Chat. The Chat action reads the CHAT_MESSAGE parameter and posts it to the configured webhook — Slack, Microsoft Teams, or Google Chat. One workflow, used by every pipeline that needs to alert.

How to adapt it

→

Different data source

Replace the Odoo Input with any other source — a database query, a Shopify Input, a CSV file. As long as your pipeline produces a chat_message field, the rest works without changes.

→

Different chat platform

Change the webhook URL in CHAT_WEBHOOK_URL to switch between Slack, Teams, and Google Chat. The message format is plain text — no platform-specific markup needed.

→

Reuse the workflow

Copy chat-slack-notifications.hwf into any project. Add a WorkflowExecutor at the end of any pipeline and point it at this workflow — instant chat alerting for any data pipeline.

What you need

Putki subscription

Access to the Odoo Input and Chat plugins, both included in all Putki tiers.

A chat webhook URL

An incoming webhook from Slack, Microsoft Teams, or Google Chat. Create one in your workspace settings and set it as the CHAT_WEBHOOK_URL parameter.

A pipeline that produces a message

Any pipeline with a final text field called chat_message can use this pattern. The overdue invoices pipeline is included as a working example.