Meeting booked - to newsletter and CRM
Configured with Cal Trigger, Google Sheets, HTTP Request, Split Out, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Transform
- Data store
- Trigger
- Web / API
- Messaging
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Split Attendees | Transform | Split Out | See node parameters |
| Add users | Data store | Google Sheets | append |
| on New Booking | Trigger | Cal Trigger | See node parameters |
| Add subscriber | Web / API | HTTP Request | POST |
| Set Attendee | Transform | Edit Fields | See node parameters |
| notify in channel | Messaging | Telegram | See node parameters |
| set data | Transform | Edit Fields | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
calApigoogleSheetsOAuth2ApitelegramApi
Workflow notes
Define your parameters
Define your parameters
- Find your telegram chat id to get notified in a private channel (bot must be added as admin)
- Create an account on Beehiiv and get your api key
- Get your publication id from your newsletter which will be parsed in the "Add subscriber" url endpoint
How it works
How it works
This workflow allows you to add each meeting guest into Google Sheets, adding one row for each guest and consequently adding those users to your newsletter on Beehiiv.
Set up steps
- Create an account on Cal.com
- Create a new webhook on Cal.com and send a test event to the URL that appears in the first node. You will get test data that you can pin to set the rest of the workflow.
- For Beehiiv you will need to get the publication id from the account plus the api key. You will find those on your account settings. Define the publication id on the "set data" node, together with your Telegram chat id, if you wish to notify yourself in a private channel when a new subscriber is added.
Enjoy building!
Aitor 1 Node
Meeting booked - to newsletter and CRM
Meeting booked - to newsletter and CRM
Purpose and structure
This folder contains the Meeting booked - to newsletter and CRM workflow. Its executable nodes use calTrigger, googleSheets, httpRequest, set, splitOut, telegram. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
on New Booking
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/2018_Telegram_Cal_Create_Webhook.json MIT; preserve source notices.