Create or update Mautic contact on a new Calendly event

Name: Create or update Mautic contact on a new Calendly event
Availability: InStock
Author: n8n Team

Create or update Mautic contact on a new Calendly event preview

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

Overview

This workflow creates or updates a Mautic contact when a new event is scheduled in Calendly. The first name and email address are the only two fields that get updated.

Prerequisites

Calendly account and Calendly credentials.
Mautic account and Mautic credentials.

How it works

Triggers on a new event in Calendly.
Creates a new contact in Mautic if the email address does not exist in Mautic.
Updates the contact's first name in Mautic if the email address exists in Mautic.

n8n Team

90 workflows

Nodes

n8n-nodes-base.calendlytrigger n8n-nodes-base.mautic n8n-nodes-base.stickynote

Complexity

beginner

Published 23 Nov 2022

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/1828/1828.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Analyze weekly Fireflies sales calls with GPT-4o-mini, Google Sheets and Slack

### Description Connect your Fireflies account once and activate the workflow — every Monday at 9AM it runs automatically without any input from you. It pulls all sales call transcripts from the past 7 days, analyzes each one with GPT-4o-mini, and extracts six intelligence fields: pricing mentions, objections, buying signals, competitor mentions, a key takeaway, and a recommended next action. Every call is logged as one row in Google Sheets and a full weekly digest is posted to your Slack channel. Built for sales managers and revenue teams who want structured call intelligence delivered without manual review. --- ## What This Workflow Does - **Fetches last 7 days of calls automatically** — Pulls up to 50 recent transcripts from Fireflies and filters to only those recorded in the past week - **Analyzes every call individually** — GPT-4o-mini reads each transcript and extracts six structured fields per call, not a generic summary - **Detects objections and buying signals** — Surfaces exactly what concerns were raised and what positive signals suggest the deal is moving forward - **Flags competitor mentions** — Identifies any competitor names or alternative products that came up across all calls this week - **Logs each call to Google Sheets** — Appends one 13-column row per call so your team has a permanent, searchable record of every sales conversation - **Delivers a weekly Slack digest** — Aggregates all calls into one report covering totals, top objections, top buying signals, and a call-by-call overview - **Exits cleanly when no calls exist** — If no transcripts are found for the week, the workflow stops silently without errors or empty Slack messages --- ## Setup Requirements ### Tools Needed - n8n instance (self-hosted or cloud) - Fireflies.ai account with API access - OpenAI account with GPT-4o-mini API access - Google Sheets (one sheet with a tab named **Sales Call Analysis**) - Slack workspace with OAuth2 app configured ### Credentials Required - Fireflies API key (pasted directly into **2. Set — Config Values** — no n8n credential needed) - OpenAI API key - Google Sheets OAuth2 - Slack OAuth2 **Estimated Setup Time: 15–20 minutes** --- ## Step-by-Step Setup 1. **Import the workflow** — Open n8n → Workflows → Import from JSON → paste the workflow JSON → click Import 2. **Get your Fireflies API key** — Log in to fireflies.ai → go to Settings → Integrations → copy your API key 3. **Fill in Config Values** — Open node **2. Set — Config Values** → replace all placeholders: | Field | What to enter | |---|---| | `YOUR_FIREFLIES_API_KEY` | Your Fireflies API key from step 2 | | `YOUR_GOOGLE_SHEET_ID` | The ID from your Google Sheet URL (the string between `/d/` and `/edit`) | | `Sales Call Analysis` | Leave as-is, or change to match your sheet tab name exactly | | `#sales-team` | Your Slack channel name including the `#` | | `YOUR COMPANY NAME` | Your company name (used in the AI prompt and Slack report) | | `salesKeywords` | Comma-separated keywords to identify sales calls (default: `sales,client,demo,proposal,pricing,onboarding,deal,contract`) | 4. **Connect OpenAI** — Open node **10. OpenAI — GPT-4o-mini Model** → click the credential dropdown → add your OpenAI API key → test the connection 5. **Create your Google Sheet** — Open Google Sheets → create a new sheet → add a tab named exactly **Sales Call Analysis** → add these 13 column headers in row 1: `Call Date`, `Meeting Title`, `Duration (min)`, `Participants`, `Overall Sentiment`, `Pricing Mentions`, `Objections`, `Buying Signals`, `Competitor Mentions`, `Key Takeaway`, `Recommended Action`, `Transcript URL`, `Logged At` 6. **Connect Google Sheets** — Open node **13. Google Sheets — Log Call Analysis** → click the credential dropdown → add Google Sheets OAuth2 → sign in with your Google account → authorize access 7. **Connect Slack** — Open node **15. Slack — Send Weekly Report** → click the credential dropdown → connect your Slack workspace via OAuth2 → invite the n8n bot to your sales channel in Slack (`/invite @n8n`) 8. **Activate the workflow** — Toggle the workflow to Active — it will run automatically every Monday at 9AM > ⚠️ **Test before Monday** — To test immediately without waiting for Monday, open node **1. Schedule — Every Monday 9AM**, click "Execute step", then run the full workflow manually from there. --- ## How It Works (Step by Step) **Step 1 — Schedule: Every Monday 9AM** This step fires the workflow automatically every Monday morning at 9AM. No manual trigger is needed. Once the workflow is active, this runs on its own every week. **Step 2 — Set: Config Values** Your Fireflies API key, Google Sheet ID, sheet tab name, Slack channel, company name, sales keywords, and the 7-day date window are all stored here. The week start and end dates are calculated automatically based on today's date so you never need to update them manually. **Step 3 — HTTP: Fetch Recent Transcripts** A request is sent to the Fireflies API using your API key. It retrieves the 50 most recent transcripts from your account, including each call's ID, title, date, duration, and participants. This is a lightweight fetch — full transcript content comes later. **Step 4 — Code: Filter Last 7 Days** The 50 transcripts are filtered down to only those recorded in the past 7 days. Each transcript that passes the filter becomes its own separate item so the next steps process each call individually. If no transcripts exist at all, a fallback result is passed forward. **Step 5 — IF: Any Transcripts Found?** This is the gate check. If transcripts were found (YES path), each one moves forward to full analysis. If no transcripts were found this week (NO path), the workflow routes to **6. Set — No Calls This Week** and stops cleanly — no errors, no empty reports. **Step 6 — Set: No Calls This Week** This step handles the empty-week case. It sets a simple message confirming no calls were recorded and the workflow ends here for that run. **Step 7 — HTTP: Fetch Full Transcript** For each call that passed the filter, a second Fireflies API request is made to retrieve the complete transcript details: all sentences with speaker labels, AI-detected pricing sentences, questions, tasks, keyword summary, overview, and sentiment percentages. **Step 8 — Code: Extract Transcript Data** The full transcript is processed here. Sentences are assembled into readable text (limited to 4,000 characters for GPT efficiency). Fireflies AI-flagged pricing sentences and question sentences are extracted separately. Sentiment percentages are converted into a single label: Positive, Mostly Positive, Mixed, or Negative. All data is packaged cleanly for the AI step. **Step 9 — AI Agent: Analyze Sales Call** GPT-4o-mini receives the call details, sentiment data, Fireflies-detected pricing sentences, keywords, overview, and the transcript excerpt. It returns exactly six fields: pricing mentions, objections, buying signals, competitor mentions, a key takeaway under 25 words, and a recommended action for the sales rep to take within 48 hours. **Step 10 — OpenAI: GPT-4o-mini Model** This is the language model powering the analysis step. It runs at temperature 0.3 for consistent, factual extraction and is capped at 800 tokens per call to keep costs predictable across the full week's batch. **Step 11 — Parser: Structured Call Analysis** This step enforces the exact six-field schema GPT-4o-mini must return. It validates that all required fields are present and correctly typed before the results move forward, preventing malformed output from reaching your sheet. **Step 12 — Code: Combine Analysis Results** The AI output is merged with the original transcript metadata (date, title, duration, participants, sentiment, transcript URL). A log timestamp is also added. This creates the complete data row that goes to both Google Sheets and the Slack aggregation step. **Step 13 — Google Sheets: Log Call Analysis** One row is appended to your Sales Call Analysis tab for every call analyzed. All 13 columns are populated: date, title, duration, participants, sentiment, pricing, objections, buying signals, competitors, key takeaway, recommended action, transcript URL, and logged-at timestamp. **Step 14 — Code: Build Weekly Slack Summary** All analyzed calls are aggregated into a single weekly digest. The code counts total calls, positive calls, calls with objections, calls with buying signals, and compiles unique competitor mentions. The top 3 objections and top 3 buying signals are pulled from across all calls. A call-by-call overview line is added for every transcript. **Step 15 — Slack: Send Weekly Report** The complete weekly digest is posted to your Slack channel. The message includes the week date range, summary totals, top objections, top buying signals, competitor mentions, and a one-line overview of every call. A footer confirms the full analysis is logged in Google Sheets. --- ## Key Features ✅ **Fully automated weekly cadence** — Runs every Monday at 9AM with zero manual input after setup ✅ **Per-call AI intelligence** — Each call gets its own six-field analysis, not a rolled-up average ✅ **Fireflies AI signals as input** — Pricing sentences and questions detected by Fireflies are fed directly into GPT for more accurate extraction ✅ **Structured output enforced** — A schema parser validates every AI response before it reaches your sheet — no broken rows ✅ **Sentiment scoring per call** — Each call is rated Positive, Mostly Positive, Mixed, or Negative based on Fireflies sentiment percentages ✅ **Competitor tracking built in** — Competitor mentions are collected across all calls and deduplicated into one list in the Slack report ✅ **48-hour action item per call** — Every call ends with one concrete action the sales rep should take — not a vague suggestion ✅ **Clean empty-week handling** — No transcripts this week means a clean stop, not an error or blank Slack message --- ## Customisation Options **Change the schedule day or time** — In node **1. Schedule — Every Monday 9AM**, edit the cron expression `0 9 * * 1` to run on a different day or time. For example, `0 8 * * 5` runs every Friday at 8AM for an end-of-week review instead. **Increase the transcript fetch limit** — In node **3. HTTP — Fetch Recent Transcripts**, change `limit: 50` in the GraphQL query body to `100` if your team records more than 50 calls per week to ensure no calls are missed. **Expand the date window beyond 7 days** — In node **2. Set — Config Values**, change `{days: 7}` in both the `weekStart` and `sevenDaysAgoMs` fields to `{days: 14}` for a bi-weekly analysis window. **Add a Slack alert for high-objection calls** — After node **12. Code — Combine Analysis Results**, add an IF check: if the `objections` field does not contain "No objections", post an immediate Slack alert to a `#deal-risk` channel so the sales manager can follow up same day. **Add a Gmail summary to the sales manager** — After node **15. Slack — Send Weekly Report**, add a Gmail node to also email the full weekly digest to your sales manager's inbox as a backup record outside of Slack. **Filter to specific call types using keywords** — In node **2. Set — Config Values**, edit the `salesKeywords` field to narrow analysis to specific call types — for example, change to `demo,discovery,closing` to analyze only those pipeline stages. --- ## Troubleshooting **Fireflies returning no transcripts or an auth error:** - Confirm `YOUR_FIREFLIES_API_KEY` in node **2. Set — Config Values** is replaced with your actual key — not the placeholder text - Get your key from fireflies.ai → Settings → Integrations → API Key - Make sure your Fireflies plan includes API access — some free plans do not **Workflow not triggering on Monday:** - Confirm the workflow is toggled to Active — it will not run on a schedule if inactive - Check that the cron expression in node **1. Schedule — Every Monday 9AM** is `0 9 * * 1` — any edit to this field can break the schedule - To test immediately, click on node 1 and use the manual Execute option **Google Sheets not logging rows:** - Confirm the Google Sheets OAuth2 credential in node **13. Google Sheets — Log Call Analysis** is connected and not expired - Check that `YOUR_GOOGLE_SHEET_ID` in node **2. Set — Config Values** matches the ID in your sheet URL exactly - Confirm the tab is named **Sales Call Analysis** exactly — capitalization and spacing must match `sheetName` in Config Values **AI returning incomplete or missing fields:** - The schema parser in node **11. Parser — Structured Call Analysis** enforces all six fields — if output is missing fields, check the execution log of node **9. AI Agent — Analyze Sales Call** for the raw GPT response - Confirm the OpenAI credential in node **10. OpenAI — GPT-4o-mini Model** is connected and your account has available credits - If transcripts are very short, GPT may have little content to extract — the fallback text ("No objections detected", etc.) will be used automatically **Slack report not arriving:** - Confirm the Slack OAuth2 credential in node **15. Slack — Send Weekly Report** is connected and authorized - Check that the channel name in node **2. Set — Config Values** includes the `#` prefix and matches your actual Slack channel name exactly - Type `/invite @n8n` in your Slack channel to ensure the bot has posting permission --- ## Support Need help setting this up or want a custom version built for your team or agency? 📧 Email: [[email protected]]([email protected]) 🌐 Website: [https://isawow.com/](https://isawow.com/)

View

Sync Salesforce leads and opportunities to PostgreSQL with backfill and incremental ETL

## Salesforce Leads & Opportunities to PostgreSQL (Backfill & Incremental Sync ETL) This workflow extracts Lead and Opportunity data from Salesforce, transforms and normalizes the data, and loads it into PostgreSQL as a structured data bank for reporting and analytics. It is designed for scalable data ingestion and supports both historical backfill and incremental sync in a single workflow. --- ### Use Case This workflow is suitable when you need to: - Centralize Salesforce data into a database for reporting - Build a data warehouse for BI tools (Looker Studio, Metabase, etc.) - Track lead-to-opportunity lifecycle - Merge multiple Salesforce objects into a unified dataset - Maintain a clean and normalized CRM data layer --- ### Two Input Modes #### 1. Historical Backfill (Manual Trigger) Run once to populate historical data. - Set start_date and end_date in the "Set Historical Date Range" node - Data is split into 7-day batches - Each batch is processed sequentially to reduce API load --- #### 2. Incremental Sync (Schedule Trigger) Runs automatically (e.g. daily). - Date range is generated dynamically using ISO datetime - Typically pulls data from yesterday until today - No manual input required --- ### Batch Processing Date ranges are processed in weekly batches. This helps: - Prevent large API requests - Reduce timeout risk - Improve stability during backfill - Keep memory usage efficient --- ### Core Workflow Logic #### 1. Data Extraction - Fetch Lead records from Salesforce - Fetch Opportunity records from Salesforce - Filter using CreatedDate (since_datetime and until_datetime) --- #### 2. Phone-Based Routing Records are split into two paths: - Records without phone: - Skip normalization - Still included in final dataset - Records with phone: - Processed for normalization - Used for merging This ensures no data is lost even if phone is missing. --- #### 3. Phone Normalization (+62) Phone numbers are standardized into: +62XXXXXXXXXX Steps: - Remove spaces and symbols - Remove all non-digit characters - Convert 0xxxx → 62xxxx - Ensure no duplicated prefix (e.g. 6262) - Add "+" prefix This uses Indonesia's International Direct Dialing (IDD) code: +62 --- #### 4. Opportunity De-duplication - Duplicate opportunities are removed - Based on normalized phone key This ensures clean merging and avoids duplicate enrichment. --- #### 5. Lead–Opportunity Merge Merge is done using normalized phone fields: - body.nomorlead - body.nomoroppty Behavior: - Lead is the primary dataset - Opportunity enriches lead Records without phone: - Still preserved - Not removed --- #### 6. Data Standardization All records are transformed into a unified schema: - Source_Object - SF_Id - CreatedDate - CreatedById - Name - Phone - Clean_Phone - Email - LeadSource - Status - StageName - OwnerId - AccountId - Amount --- #### 7. Upsert to PostgreSQL - Uses UPSERT (insert or update) - Matching key: sf_id Behavior: - New data → insert - Existing data → update Ensures: - No duplicate records - Idempotent execution --- ### Data Flow Summary Salesforce (Lead + Opportunity) → Date Filtering → Batch Processing (weekly) → Phone Routing → Phone Normalization (+62) → Opportunity Deduplication → Lead–Opportunity Merge → Data Standardization → PostgreSQL (Upsert) --- ### Setup Requirements Before using this workflow, prepare the following: #### 1. Salesforce - Salesforce OAuth2 credential - Access to: - Lead object - Opportunity object - Ensure API access is enabled --- #### 2. PostgreSQL - Active PostgreSQL database - Credentials configured in n8n - Table created (see schema below) --- #### 3. n8n Environment - n8n instance (cloud or self-hosted) - Salesforce node configured - PostgreSQL node configured --- #### 4. Date Configuration (Backfill) - Set start_date and end_date manually in: "Set Historical Date Range" node --- #### 5. Schedule Configuration (Incremental) - Configure Schedule Trigger - Recommended: - Daily execution - Off-peak hours --- ### Minimal PostgreSQL Table Schema CREATE TABLE n8n_salesforce_data ( sf_id TEXT PRIMARY KEY, Source_Object TEXT, CreatedDate TIMESTAMP, CreatedById TEXT, Name TEXT, Phone TEXT, Clean_Phone TEXT, Email TEXT, LeadSource TEXT, Status TEXT, StageName TEXT, OwnerId TEXT, AccountId TEXT, Amount NUMERIC, synced_at TIMESTAMP DEFAULT NOW() ); --- ### Important Notes - sf_id is used as the unique key for upsert - Clean_Phone is recommended for indexing if used in analytics - Data consistency depends on phone normalization quality - Schema must be updated manually if additional fields are added --- ### Known Limitations - Phone-based matching may fail if: - Phone numbers are inconsistent - Phone is missing in both Lead and Opportunity - No deduplication for Leads (only Opportunities handled) - No retry logic for API failures (can be added) --- ### Recommended Improvements - Add index on Clean_Phone for faster queries - Add logging table for monitoring ETL runs - Add retry and error handling nodes - Extend support for: - Contact - Account - Campaign data --- ### Summary This workflow provides a reliable and scalable way to: - Extract Salesforce data - Normalize and merge datasets - Store structured data in PostgreSQL - Enable analytics and reporting pipelines It is best suited for teams building a lightweight data warehouse layer on top of Salesforce.

View

Invite the Fireflies recording bot to meetings from a one-click form

## Description Paste your meeting link into a simple form and submit. The workflow instantly sends your Fireflies recording bot to the meeting — no dashboard login, no navigation, no clicking through menus. You get a confirmation page showing the meeting title and a reminder to check your Fireflies dashboard after the call. Built for sales teams, account managers, and consultants who run back-to-back calls and cannot afford to forget recording. --- ## What This Workflow Does - **One-click bot invite** — submits a meeting link directly to the Fireflies API so the bot joins without you opening the Fireflies dashboard - **Input validation** — checks the meeting link is non-empty and starts with http before sending anything, returning an instant error if the link is invalid - **Smart defaults** — fills in a default title, 60-minute duration, and English language if you leave fields blank so nothing fails silently - **Duration clamping** — automatically keeps duration between 15 and 120 minutes regardless of what number you type - **Instant confirmation page** — shows your meeting title and duration in a clean HTML page the moment the bot is invited - **Form bookmark** — the trigger is a hosted n8n form you can bookmark and share with your whole team, no logins required --- ## Setup Requirements ### Tools you need: - n8n instance (self-hosted or n8n Cloud) - Fireflies account with API access (app.fireflies.ai) - Fireflies Personal API Key **Estimated Setup Time: 5–10 minutes** --- ## Step-by-Step Setup 1. **Get your Fireflies API key** — Log in to app.fireflies.ai. Go to **Integrations**, then **API**. Copy your Personal API Key. 2. **Paste the API key into the HTTP node** — Open the node named **4. HTTP — Send to Fireflies API**. Find the Authorization header. Replace `YOUR_FIREFLIES_API_KEY` with the key you copied. The full value should read: `Bearer YOUR_FIREFLIES_API_KEY` with your actual key in place of the placeholder. 3. **Update the default meeting title** — Open the node named **2. Set — Validate and Prepare Inputs**. Find the `meeting_title` assignment. Change `Sales Meeting - Incrementors` to your own default title, such as your company name or team name. 4. **Activate the workflow** — Click Activate in the top right. Copy the form URL from node **1. Form — Invite Fireflies Bot** and bookmark it or share it with your team. --- ## How It Works (Step by Step) **Step 1 — Form Trigger: Invite Fireflies Bot** You open the form in your browser and fill in five fields: the meeting link, an optional title, an optional password, the duration in minutes, and the language. When you submit, the workflow starts. The form is hosted by n8n and accessible from any browser without any login. **Step 2 — Set: Validate and Prepare Inputs** This step cleans every field you submitted. It trims whitespace from the meeting link. If you left the title blank, it sets the default to `Sales Meeting - Incrementors`. If you left the duration blank or typed something invalid, it defaults to 60 minutes. It also clamps the duration so it is never below 15 or above 120 minutes. Language defaults to English if nothing was selected. **Step 3 — IF: Valid Meeting Link?** This step checks two things: the meeting link must not be empty, and it must start with `http`. If both conditions are true, the workflow continues to the Fireflies API call. If either condition fails — for example, you pasted a link without `https://` — the workflow routes to the error path. The error path (nodes 7 and 8) returns an error page to you immediately. *(Note: the error response nodes are referenced in the workflow overview but are not yet wired in the connections — see Troubleshooting below.)* **Step 4 — HTTP Request: Send to Fireflies API** This step sends a GraphQL mutation to `https://api.fireflies.ai/graphql`. It passes your meeting link, title, password, duration, and language. Fireflies responds and the bot is dispatched to join your meeting at the specified link. **Step 5 — Set: Build Success Response** This step builds a confirmation HTML page using the meeting title and duration from Step 2. It formats them into a clean green card with a checkmark so you know the bot was invited successfully. **Step 6 — Respond: Bot Invited Successfully** This step returns the confirmation HTML page directly in your browser. You see the meeting title and duration, and a note reminding you the transcript will appear in your Fireflies dashboard after the call ends. The workflow is complete. --- ## Key Features ✅ **Bookmarkable form URL** — share a single link with your whole team; no one needs access to n8n or Fireflies directly ✅ **Instant link validation** — invalid or missing links are caught before the API is called, preventing silent failures ✅ **Duration clamping** — no matter what number a user types, duration is always kept within the 15–120 minute range Fireflies accepts ✅ **Sensible defaults** — blank fields never cause errors; title, duration, and language all fall back to safe defaults automatically ✅ **Confirmation page** — submitter sees exactly which meeting was booked and for how long, reducing doubt and repeat submissions ✅ **Multi-language support** — form includes English, Hindi, Spanish, French, and Portuguese so international teams can use it out of the box ✅ **Zero-login experience** — the bot is invited from a public form; your team never needs to open Fireflies or n8n --- ## Customisation Options **Add more languages to the dropdown** — Open node **1. Form — Invite Fireflies Bot**, find the Meeting Language field, and add new language codes such as `de`, `it`, or `ja` to the options list. **Change the default meeting title** — Open node **2. Set — Validate and Prepare Inputs** and update `Sales Meeting - Incrementors` to match your company or team name. This appears on the confirmation page. **Extend the maximum duration** — In node **2. Set — Validate and Prepare Inputs**, find the `meeting_duration` expression and change `120` to a higher number if your calls regularly run longer than two hours. **Wire up the error response path** — Nodes 7 and 8 (error response) exist in the overview but are not yet connected. Add a **Set** node and a **Respond to Webhook** node connected to the false path of node **3. IF — Valid Meeting Link?** to show users a clear error message when their link is invalid. **Log every submission to Google Sheets** — Add a Google Sheets node after node **4. HTTP — Send to Fireflies API** to record each meeting link, title, and timestamp for your CRM or sales tracking. **Send a Slack notification on invite** — Add a Slack node after node **5. Set — Build Success Response** to ping your sales channel every time a bot is dispatched, keeping the team aware of active calls. --- ## Troubleshooting **API key not working:** - Confirm you replaced the full placeholder `YOUR_FIREFLIES_API_KEY`, not just part of it - The Authorization header value must be exactly `Bearer ` followed by your key with a space between them - Check that your Fireflies account has API access enabled under Integrations **Bot not joining the meeting:** - Confirm the meeting link is a live, future meeting — Fireflies cannot join meetings that have already ended - Check that the meeting platform is supported by Fireflies (Google Meet, Zoom, Microsoft Teams, Webex) - If the meeting requires a password, make sure you filled in the password field on the form **Form submits but nothing happens:** - Confirm the workflow is Activated — inactive workflows do not process form submissions - Open the n8n execution log to see which node failed and what error message it returned **Error page not showing for invalid links:** - The error response path (nodes 7 and 8) is defined in the overview but is not connected in the current workflow — the false path of node **3. IF — Valid Meeting Link?** has no output wired. Connect a Set node and a Respond to Webhook node to that path to return a proper error page. **Duration defaulting to unexpected values:** - If you type a non-numeric value in the Duration field, the workflow defaults to 60 minutes. This is intentional. If 60 is not the right default for your team, update the fallback value in node **2. Set — Validate and Prepare Inputs**. --- ## Support Need help setting this up or want a custom version built for your team or agency? 📧 Email: [[email protected]]([email protected]) 🌐 Website: [https://isawow.com/](https://isawow.com/)

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Create or update Mautic contact on a new Calendly event

Workflow preview

Important notice

Overview

Prerequisites

How it works