Who is this for Teams using Pennylane (French accounting platform) who want automatic alerts when invoices are paid or become overdue, without checking Pennylane manually. What it does This workflow runs every 15 minutes, fetches all customer invoices from Pennylane, and classifies them as paid, overdue, or upcoming. If any invoices have been paid or are overdue, it sends a summary notification to Slack. If everything is normal, the workflow ends silently. How to set up Import this workflow into n8n Create a Header Auth credential with name Authorization and value Bearer <YOUR_PENNYLANE_TOKEN> Select your Slack channel in the SL Send Notification node Adjust the schedule interval in the Schedule Trigger node if needed Requirements Pennylane account with API access (Essentiel plan or higher) Pennylane API token with scope: customer_invoices:all (Optional) Slack workspace for notifications How to customize Change the polling interval in the Schedule Trigger node (default: every 15 minutes) Replace Slack with Telegram, Email, or any other notification channel Note: Pennylane API does not support filtering by status or paid fields, all classification is done client-side in a Code
Tags
Related workflows
See all Slack→Alert on API contract drift using Data Tables and Slack
Quick overview This workflow runs on a schedule, polls a JSON API endpoint, derives and stores a snapshot of the response schema in an n8n Data Table, and posts a Slack alert only when the response structure or field types change. How it works Runs every 6 hours on a schedule. Loads the configured API endpoint URL, an endpoint key used for snapshotting, and the target Slack channel. Fetches the endpoint with retries and skips the run if the response is not a valid JSON object or array. Derives a normalized schema (field paths, types, required/optional, and nullability) and compares it to the previous schema stored in an n8n Data Table. Upserts the latest schema snapshot back into the n8n Data Table under the same endpoint key. Posts a formatted drift report to Slack only when a high- or medium-severity contract change is detected. Setup Create an n8n Data Table (for example, “API Contract Snapshots”) with text columns named endpointKey and schema_object, and select its ID in both the read and upsert steps. Add a Slack API credential in n8n. Update the Settings values for endpointUrl, endpointKey, and slackChannel (Slack channel ID) to match your API and destination channel. Run the
Monitor target account funding, acquisitions, and exec moves with Datahyena and Slack
Quick overview This workflow runs every morning and checks Datahyena for funding events, acquisitions, and executive moves from the last 24 hours, then posts matching updates for your target account domains to a Slack channel. How it works Runs every day at 9:00 AM. Loads a list of target company domains to monitor. Fetches the last 24 hours of funding events from the Datahyena API, filters to events where the company domain matches your target list, and posts each match to Slack. Fetches the last 24 hours of acquisition events from the Datahyena API, filters to deals where either the acquirer or target domain matches your list, and posts each match to Slack. Fetches the last 24 hours of executive move events from the Datahyena API, filters to moves where the current or previous company domain matches your list, and posts each match to Slack. Setup Create a Datahyena API key and configure an HTTP Header Auth credential with header name X-API-Key for the three Datahyena HTTP requests. Update the target domain list in the workflow’s target accounts step (the domains array). Connect your Slack credential and select the channel for the three Slack message steps.
Notify Slack about new marketplace templates with the n8n Templates API
Quick overview This workflow runs every two hours to check the n8n public Templates API for the latest workflows in a chosen category, tracks which template IDs have already been seen using workflow static data, and posts a Slack digest when new templates appear. How it works Runs on a schedule every 2 hours. Loads configuration values such as the template category slug, the Slack channel, how many templates to check, and whether to report when none are new. Calls the n8n Templates search API to fetch the most recent templates for the configured category. Extracts key metadata (ID, title, description snippet, creator, date, and URL) from the API response. Compares the fetched template IDs against previously seen IDs stored in workflow static data and updates the cache with the latest IDs. If new templates are found, formats a Slack digest and posts it to the configured Slack channel. If no new templates are found and reporting is enabled, posts a “no new templates” all-clear message to Slack. Setup Add Slack credentials in n8n with permission to post messages to your target channel. Update the Configuration values for categorySlug and slackChannel (and optionally templatesToCheck a