Setup guides

Everything you need to connect your automation tools to Pipewatch and start monitoring. Each guide takes under 5 minutes.

Connect Make

Generate an API key in your Make account and paste it into Pipewatch. Pipewatch will automatically import all your scenarios.

Go to your Make profile settings

Log into Make at make.com. Click your avatar in the bottom-left corner → select Profile.

Open the API tab

In your profile page, click the API tab in the top navigation. You'll see a list of your existing API tokens (may be empty).

Create a new token

Click Add token. Give it a name like Pipewatch. Leave the scopes at their defaults — Pipewatch only reads your scenario data, it never modifies anything.

Tip: If you manage multiple Make accounts (e.g. one per client), repeat this process for each account and add them as separate integrations in Pipewatch.

Copy your API token

Make will show the token once. Copy it immediately — you won't be able to see it again.

mk-xxxxxxxxxxxxxxxxxxxxxxxxxxxx ← copy this

Note your Make zone

Check the URL in your browser while logged into Make. Your zone is the subdomain:

https://eu2.make.com/...  ← zone is "eu2"
https://us1.make.com/...  ← zone is "us1"

Paste into Pipewatch

Go to Integrations in Pipewatch → click Connect Make → paste your API token and select your zone → click Connect. Pipewatch will automatically import all your scenarios within seconds.

Done! Your Make scenarios will appear in your dashboard. Pipewatch will start monitoring them immediately.

Make execution history limits
Pipewatch fetches up to 50 executions per scenario per sync — this is the maximum Make's API allows. Make retains execution logs for 30 days on most plans. Executions older than 30 days are not available via the API, regardless of your Pipewatch plan. If you just connected Make, history from before the connection date may be partially or fully unavailable depending on your Make plan.

Connect n8n

Works with both n8n Cloud and self-hosted n8n instances. You'll need an API key and your instance URL.

Log into your n8n instance

For n8n Cloud: go to app.n8n.cloud.
For self-hosted: open your instance URL (e.g. http://your-server:5678).

Go to Settings → API

Click your avatar or name in the bottom-left → Settings → select API from the left menu.

Enable the API and create a key

Toggle on Enable API if it isn't already. Then click Create an API Key. Give it the label Pipewatch. Copy the key shown.

n8n_api_xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Note: The n8n API must be enabled for Pipewatch to connect. If you don't see the API option, check that your n8n instance is version 0.198.0 or later.

Find your instance base URL

This is the root URL of your n8n instance — no trailing slash:

n8n Cloud:    https://app.n8n.cloud
Self-hosted:  http://192.168.1.10:5678
Custom domain:https://n8n.yourdomain.com

Paste into Pipewatch

Go to Integrations → click Connect n8n → paste your API key and your base URL → click Connect.

Done! All your n8n workflows will be imported automatically. If your instance is self-hosted on an internal network, the "Open in n8n" deep link will only work when you're on that network.

n8n execution history limits
Pipewatch fetches up to 100 executions per workflow per sync — the maximum n8n's API allows. Retention depends on your setup:

n8n Cloud: 7 days (Starter) · 30 days (Pro) · Unlimited (Enterprise)
Self-hosted: 14 days by default (configurable via EXECUTIONS_DATA_MAX_AGE). Executions are also pruned when the total count exceeds 10,000.

Executions outside the retention window are permanently deleted by n8n and cannot be retrieved.

Connect Zapier

Connect your Zapier account using a personal API key. Pipewatch will monitor your Zaps' status and alert you when they fail.

Note: Zapier's API does not expose execution logs. Pipewatch monitors Zap status (on/off/error) but cannot show individual run history for Zapier. Use the "Open in Zapier" link to view detailed logs directly.

Go to your Zapier Developer settings

Log into zapier.com. Go to developer.zapier.com/credentials directly, or navigate to Settings → API Credentials.

Generate a personal API key

Click Generate Token. Copy the key shown — it won't be displayed again.

zapier-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Paste into Pipewatch

Go to Integrations → click Connect Zapier → paste your API key → click Connect.

Done! Your Zaps will be imported and monitored. Pipewatch checks their status every 5 minutes.

Set up Slack alerts

Create a Slack webhook to receive instant alerts when any workflow fails or recovers. Takes under 3 minutes.

Create a new Slack app

Go to api.slack.com/apps → click Create New App → select From scratch. Name it Pipewatch and select your workspace.

Enable Incoming Webhooks

In your app settings, click Incoming Webhooks in the left sidebar. Toggle Activate Incoming Webhooks to On.

Add a webhook to your workspace

Scroll down and click Add New Webhook to Workspace. Select the Slack channel where you want to receive alerts (e.g. #pipewatch-alerts) → click Allow.

Tip: Create a dedicated channel like #pipewatch-alerts so alerts don't get mixed with other messages. You can create one per client folder for agency use.

Copy your webhook URL

After authorizing, Slack generates a webhook URL. Copy it — it looks like this:

https://hooks.slack.com/services/T.../B.../xxxx

Paste into Pipewatch

Go to Settings → Notifications in Pipewatch. Paste your webhook URL → add the channel name for display (e.g. #pipewatch-alerts) → click Connect Slack. Pipewatch will send a test message to confirm.

Done! You'll now receive a Slack alert within 60 seconds of any workflow failure, with the error message and AI diagnosis included.