# Morning Slack digest of your Fivetran pipeline health

> Every weekday morning we check your Fivetran data pipelines and post a Slack digest that leads with what's broken, flags stale or paused syncs, and confirms the rest are healthy.

- Workflow type: agent
- Services: Fivetran, Slack Bot
- Categories: Operations, Engineering
- Published: 2026-07-17

## What it does

- Checks the sync status of every data pipeline in your Fivetran account each weekday morning.
- Writes a short, skimmable Slack digest that puts broken or failing pipelines first.
- Calls out pipelines that look stale or paused, then confirms the rest are running normally.
- Posts the summary to your data team's Slack channel so everyone starts the day knowing what needs attention.

## What you'll need

- A Fivetran account with the data pipelines you want to monitor.
- A Slack workspace and the channel where the morning digest should be posted.

## Prompt

Every weekday morning at 8am, give me a health check of all my Fivetran data pipelines and post it to my data team's Slack channel so they start the day knowing exactly what needs attention. Use a cron trigger set to Monday through Friday at 8am.

First, use Fivetran's List Connections operation to retrieve every connection in the account. Fivetran wraps the results under data.items, and each connection carries a status object. Read its sync_state and setup_state, the last successful sync timestamp (succeeded_at, and failed_at when present), and whether the connection is paused. One call enumerates the health of the whole account, so page through with the cursor if there is more than one page of results.

For any connection that looks broken or ambiguous, you can call Get Connection or Get Connection State to pull extra detail before writing it up.

Then write a short, skimmable digest grouped by status, ordering broken pipelines first. Lead with any connection that is broken or failing, meaning a sync_state of error or broken, a failed last sync, or a setup that never finished. Next, call out anything that looks stale or paused, such as paused connections and connections whose last successful sync is well past their normal schedule (for example, no successful sync in over a day). Finally, confirm the rest are healthy with a brief count. For each flagged pipeline, name it by its source and destination or schema name, say what is wrong, and note when it last synced. Keep it scannable with clear status groupings and short lines.

Send the finished digest to the data team's Slack channel using Slack Bot's Send a Message operation. Format it with Slack mrkdwn so the status groups and pipeline names are easy to scan, and keep the wording plain by saying 'data pipelines' rather than 'connectors'.

## How to customize

- Change the schedule, for example run it at 7am or include weekends.
- Pick which Slack channel or direct message receives the digest.
- Adjust what counts as stale, for example flag any pipeline that hasn't synced successfully in over a day.

## Example output

Fivetran pipeline health — Thursday 8:00am

🔴 Needs attention (2 broken)
• Salesforce → Snowflake: last sync failed 6h ago (connection error)
• Stripe → BigQuery: sync error, no successful sync in 2 days

🟡 Keep an eye on (2)
• HubSpot → Snowflake: paused
• Zendesk → BigQuery: last successful sync 3 days ago (stale)

🟢 Healthy (14)
All other pipelines synced successfully in the last few hours.

## FAQ

### What counts as a broken pipeline?

Any data pipeline whose most recent sync failed or is in an error state. Those are listed first in the digest so your team can jump on them right away.

### Will it still message me if everything is healthy?

Yes. You'll get a short confirmation each morning that all your pipelines synced successfully, so no news really is good news.

### Can it post to a private Slack channel?

Yes, as long as the Slack bot has been added to that channel. You choose whichever channel or direct message the digest is sent to.

### How often does it run?

By default it runs every weekday morning at 8am, but you can change the time or days to match your team's schedule.

### Do I need to list my pipelines manually?

No. It automatically finds every data pipeline in your Fivetran account, so newly added pipelines are covered the moment you create them.

Use this prompt in General Input: https://www.generalinput.com/prompts/morning-slack-digest-of-your-fivetran-pipeline-health