Create, update and get a user from Iterable
Iterable User Management Workflow
This n8n workflow provides a robust solution for managing user profiles within Iterable. It demonstrates how to create, update, and retrieve user information, making it a foundational tool for synchronizing user data between your systems and Iterable.
What it does
This workflow showcases the core functionalities of the Iterable node in n8n, specifically focusing on user management:
- Starts the workflow: Initiates the execution of the workflow.
- Manages Iterable Users: Utilizes the Iterable node to interact with your Iterable account. While the specific operation (create, update, or get) is not explicitly defined in the provided JSON, the node's presence indicates its capability to perform these actions based on its configuration.
Prerequisites/Requirements
- n8n Instance: A running instance of n8n.
- Iterable Account: An active Iterable account.
- Iterable API Key: An API key from your Iterable account configured as an n8n credential.
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure Iterable Credentials:
- In the n8n workflow editor, locate the "Iterable" node.
- Click on the "Credential" field and select "Create New" if you haven't already.
- Choose "Iterable API" as the credential type.
- Enter your Iterable API Key (found in your Iterable project settings) into the "API Key" field.
- Save the credential.
- Configure the Iterable Node:
- The "Iterable" node is currently set up to interact with user data.
- To create a user, set the "Operation" to "Create" and provide the necessary user data (e.g.,
email,userId,dataFields). - To update a user, set the "Operation" to "Update" and provide the user identifier and the
dataFieldsto update. - To get a user, set the "Operation" to "Get" and provide the user identifier.
- You will need to manually configure the specific "Operation" and "Parameters" within the Iterable node's settings to match your desired action (create, update, or get a user).
- Activate the Workflow: Once configured, activate the workflow to enable it to run. You can then trigger it manually or connect it to another trigger node for automation.
Related Templates
AI meeting summary & action item tracker with Notion, Slack, and Gmail
How it Works This workflow accepts meeting transcripts via webhook (Zoom, Google Meet, Teams, Otter.ai, or manual notes), immediately processing them through an intelligent pipeline that eliminates post-meeting admin work. The system parses multiple input formats (JSON, form data, transcription outputs), extracting meeting metadata including title, date, attendees, transcript content, duration, and recording URLs. OpenAI analyzes the transcript to extract eight critical dimensions: executive summary, key decisions with ownership, action items with assigned owners and due dates, discussion topics, open questions, next steps, risks/blockers, and follow-up meeting requirements—all returned as structured JSON. The intelligence engine enriches each action item with unique IDs, priority scores (weighing urgency + owner assignment + due date), status initialization, and meeting context links, then calculates a completeness score (0-100) that penalizes missing owners and undefined deadlines. Multi-channel distribution ensures visibility: Slack receives formatted summaries with emoji categorization for decisions (✅), action items (🎯) with priority badges and owner assignments, and completeness scores (📊). Notion gets dual-database updates—meeting notes with formatted decisions and individual task cards in your action item database with full filtering and kanban capabilities. Task owners receive personalized HTML emails with priority color-coding and meeting context, while Google Calendar creates due-date reminders as calendar events. Every meeting logs to Google Sheets for analytics tracking: attendee count, duration, action items created, priority distribution, decision count, completeness score, and follow-up indicators. The workflow returns a JSON response confirming successful processing with meeting ID, action item count, and executive summary. The entire pipeline executes in 8-12 seconds from submission to full distribution. --- Who is this for? Product and engineering teams drowning in scattered action items across tools Remote-first companies where verbal commitments vanish after calls Executive teams needing auditable decision records without dedicated note-takers Startups juggling 10+ meetings daily without time for manual follow-up Operations teams tracking cross-functional initiatives requiring accountability --- Setup Steps Setup time: 25-35 minutes Requirements: OpenAI API key, Slack workspace, Notion account, Google Workspace (Calendar/Gmail/Sheets), optional transcription service Webhook Trigger: Automatically generates URL, configure as POST endpoint accepting JSON with title, date, attendees, transcript, duration, recording_url, organizer Transcription Integration: Connect Otter.ai/Fireflies.ai/Zoom webhooks, or create manual submission form OpenAI Analysis: Add API credentials, configure GPT-4 or GPT-3.5-turbo, temperature 0.3, max tokens 1500 Intelligence Synthesis: JavaScript calculates priority scores (0-40 range) and completeness metrics (0-100), customize thresholds Slack Integration: Create app with chat:write scope, get bot token, replace channel ID placeholder with your meeting-summaries channel Notion Databases: Create "Meeting Notes" database (title, date, attendees, summary, action items, completeness, recording URL) and "Action Items" database (title, assigned to, due date, priority, status, meeting relation), share both with integration, add token Email Notifications: Configure Gmail OAuth2 or SMTP, customize HTML template with company branding Calendar Reminders: Enable Calendar API, creates events on due dates at 9 AM (adjustable), adds task owner as attendee Analytics Tracking: Create Google Sheet with columns for MeetingID, Title, Date, Attendees, Duration, ActionItems, HighPriority, Decisions, Completeness, UnassignedTasks, FollowUpNeeded Test: POST sample transcript, verify Slack message, Notion entries, emails, calendar events, and Sheets logging --- Customization Guidance Meeting Types: Daily standups (reduce tokens to 500, Slack-only), sprint planning (add Jira integration), client calls (add CRM logging), executive reviews (stricter completeness thresholds) Priority Scoring: Add urgency multiplier for <48hr due dates, owner seniority weights, customer impact flags AI Prompt: Customize to emphasize deadlines, blockers, or technical decisions; add date parsing for phrases like "by end of week" Notification Routing: Critical priority (score >30) → Slack DM + email, High (20-30) → channel + email, Medium/Low → email only Tool Integrations: Add Jira/Linear for ticket creation, Asana/Monday for project management, Salesforce/HubSpot for CRM logging, GitHub for issue creation Analytics: Build dashboards for meeting effectiveness scores, action item velocity, recurring topic clustering, team productivity metrics Cost Optimization: ~1,200 tokens/meeting × $0.002/1K (GPT-3.5) = $0.0024/meeting, use batch API for 50% discount, cache common patterns --- Once configured, this workflow becomes your team's institutional memory—capturing every commitment and decision while eliminating hours of weekly admin work, ensuring accountability is automatic and follow-through is guaranteed. --- Built by Daniel Shashko Connect on LinkedIn
By Daniel ShashkoAutomated product price tracking with ScrapeGraphAI, Slack alerts and Jira tickets
Product Price Monitor with Slack and Jira ⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n instance before using this template. This workflow automatically scrapes multiple e-commerce sites, analyses weekly seasonal price trends, and notifies your team in Slack while opening Jira tickets for items that require price adjustments. It helps retailers plan inventory and pricing by surfacing actionable insights every week. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or n8n cloud) ScrapeGraphAI community node installed Slack workspace & channel for notifications Jira Software project (cloud or server) Basic JavaScript knowledge for optional custom code edits Required Credentials ScrapeGraphAI API Key – Enables web scraping Slack OAuth Access Token – Required by the Slack node Jira Credentials – Email & API token (cloud) or username & password (server) (Optional) Proxy credentials – If target websites block direct scraping Specific Setup Requirements | Resource | Purpose | Example | |----------|---------|---------| | Product URL list | Seed URLs to monitor | https://example.com/products-winter-sale | | Slack Channel | Receives trend alerts | pricing-alerts | | Jira Project Key | Tickets are created here | ECOM | How it works This workflow automatically scrapes multiple e-commerce sites, analyses weekly seasonal price trends, and notifies your team in Slack while opening Jira tickets for items that require price adjustments. It helps retailers plan inventory and pricing by surfacing actionable insights every week. Key Steps: Webhook Trigger: Kicks off the workflow via a weekly schedule or manual call. Set Product URLs: Prepares the list of product pages to analyse. SplitInBatches: Processes URLs in manageable batches to avoid rate limits. ScrapeGraphAI: Extracts current prices, stock, and seasonality hints from each URL. Code (Trend Logic): Compares scraped prices against historical averages. If (Threshold Check): Determines if price deviations exceed ±10%. Slack Node: Sends a formatted message to the pricing channel for each deviation. Jira Node: Creates/updates a ticket linking to the product for further action. Merge: Collects all batch results for summary reporting. Set up steps Setup Time: 15-20 minutes Install Community Nodes: In n8n, go to Settings → Community Nodes, search for “ScrapeGraphAI”, and install. Add Credentials: a. Slack → Credentials → New, paste your Bot/User OAuth token. b. Jira → Credentials → New, enter your domain, email/username, API token/password. c. ScrapeGraphAI → Credentials → New, paste your API key. Import Workflow: Upload or paste the JSON template into n8n. Edit the “Set Product URLs” Node: Replace placeholder URLs with your real product pages. Configure Schedule: Replace the Webhook Trigger with a Cron node (e.g., every Monday 09:00) or keep as webhook for manual runs. Map Jira Fields: In the Jira node, ensure Project Key, Issue Type (e.g., Task), and Summary fields match your instance. Test Run: Execute the workflow. Confirm Slack message appears and a Jira issue is created. Activate: Toggle the workflow to Active so it runs automatically. Node Descriptions Core Workflow Nodes: Webhook – Default trigger, can be swapped with Cron for weekly automation. Set (Product URLs) – Stores an array of product links for scraping. SplitInBatches – Limits each ScrapeGraphAI call to five URLs to reduce load. ScrapeGraphAI – Crawls and parses HTML, returning JSON with title, price, availability. Code (Trend Logic) – Calculates percentage change vs. historical data (stored externally or hard-coded for demo). If (Threshold Check) – Routes items above/below the set variance. Slack – Posts a rich-format message containing product title, old vs. new price, and link. Jira – Creates or updates a ticket with priority set to Medium and assigns to the Pricing team lead. Merge – Recombines batch streams for optional reporting or storage. Data Flow: Webhook → Set (Product URLs) → SplitInBatches → ScrapeGraphAI → Code (Trend Logic) → If → Slack / Jira → Merge Customization Examples Change Price Deviation Threshold javascript // Code (Trend Logic) node const threshold = 0.05; // 5% instead of default 10% Alter Slack Message Template javascript { "text": ${item.name} price changed from $${item.old} to $${item.new} (${item.diff}%)., "attachments": [ { "title": "Product Link", "title_link": item.url, "color": "4E79A7" } ] } Data Output Format The workflow outputs structured JSON data: json { "product": "Winter Jacket", "url": "https://example.com/winter-jacket", "oldPrice": 129.99, "newPrice": 99.99, "change": -23.06, "scrapedAt": "2023-11-04T09:00:00Z", "status": "Below Threshold", "slackMsgId": "A1B2C3", "jiraIssueKey": "ECOM-101" } Troubleshooting Common Issues ScrapeGraphAI returns empty data – Verify selectors; many sites use dynamic rendering, require a headless browser flag. Slack message not delivered – Check that the OAuth token scopes include chat:write; also confirm channel ID. Jira ticket creation fails – Field mapping mismatch; ensure Issue Type is valid and required custom fields are supplied. Performance Tips Batch fewer URLs (e.g., 3 instead of 5) to reduce timeout risk. Cache historical prices in an external DB (Postgres, Airtable) instead of reading large CSVs in the Code node. Pro Tips: Rotate proxies/IPs within ScrapeGraphAI to bypass aggressive e-commerce anti-bot measures. Add a Notion or Sheets node after Merge for historical logging. Use the Error Trigger workflow in n8n to alert when ScrapeGraphAI fails more than X times per run.
By vinci-king-01Website downtime monitoring with smart alerts via Telegram & Email
Get ==Instant== Alerts When Your Website Goes Down — Using ==n8n== as ==Website Downtime Checker Robot== If you manage websites (your own or clients’), downtime alerts are critical. But most monitoring tools create alert fatigue — ==emails for every tiny hiccup==, even 30–60 second outages. This setup shows how to use n8n as a smart uptime monitor: ✅ No extra subscriptions ✅ No false-positive spam ✅ Alerts only for real downtime ✅ Optional instant phone notifications Why Use n8n for Website Monitoring? Traditional tools like Uptime Robot become limiting or expensive as you scale. With n8n, you get: Full control over alert logic Custom timing & thresholds No forced notification rules One tool for uptime and other automations You decide when, how, and why alerts are sent. Quick Start: Free n8n Website Monitoring Workflow Get running in minutes: Use the prebuilt n8n template Sign up for n8n Cloud or self-host for free Set your schedule (default: hourly) Add the websites you want to monitor Key Setting (Important) Wait time: ==300 seconds (5 minutes)== >Recommended* If a site goes down, the workflow waits before alerting. ➡️ Short hiccups = ignored ➡️ Real outages = ==alerted== How to Test & Use Activate the workflow Toggle it on — monitoring runs automatically. Test instantly Add a fake or non-existent URL and run the workflow. After the wait period, you’ll receive an alert. Stay organized Alerts arrive cleanly in your inbox (Tip: pair with an AI email labeling workflow for color-coded alerts) Get Critical Alerts on Your Phone (Telegram) Email is fine — but critical sites need instant mobile alerts. Best option: Telegram bots Free Fast No extra APIs or subscriptions How It Works Create a Telegram bot via BotFather Add the bot token & chat ID to n8n Receive downtime alerts instantly on your phone No missed notifications. No noise. FAQ Can I monitor unlimited sites? > ==Yes== — just add more URLs. What about short downtime (seconds)? > Filtered out by the 5-minute wait. Do I need a paid n8n plan? > ==No.== Self-hosting is ==free==, and this works on free plans. Why not SMS or WhatsApp? > Telegram is ==faster, simpler, and doesn’t require paid APIs.== 📩 Contact Me If you have any questions, ideas to share, or would like to collaborate on a project, feel free to reach out. I’m always open to meaningful discussions, feedback, and new opportunities. 🔗 ==Connect with me== Facebook LinkedIn 💬 You’re welcome to send me a message on any platform, and I’ll get back to you as soon as possible.
By Muntasir Mubin