http request and receive google calendar events and filter out myself
Configured with Aggregate, Filter, Gmail, Google Calendar Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Trigger
- Routing
- Transform
- 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 |
|---|---|---|---|
| Research Company | Web / API | HTTP Request | See node parameters |
| Research Person | Web / API | HTTP Request | See node parameters |
| Google Calendar Trigger | Trigger | Google Calendar Trigger | See node parameters |
| Filter Out Myself | Routing | Filter | See node parameters |
| Split Out Attendees | Transform | Split Out | See node parameters |
| For Each Attendee | Routing | Loop Over Items | See node parameters |
| Is Company Email? | Routing | If | See node parameters |
| Combine All Research | Transform | Aggregate | See node parameters |
| Collect Fields | Transform | Edit Fields | See node parameters |
| Write HTML | Transform | Markdown | See node parameters |
| Edit Fields | Transform | Edit Fields | See node parameters |
| Send Report | Messaging | Gmail | See node parameters |
| Person Prompt | Transform | Edit Fields | See node parameters |
| Company Prompt | 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
gmailOAuth2googleCalendarOAuth2ApihttpHeaderAuth
Workflow notes
1. New Google Calendar Event Detected
1. New Google Calendar Event Detected
Our workflow is triggered when a new calendar event comes in.
The event gives us access to a list of attendees which we can loop over in the next step. We need to filter out ourselves if we are in the meeting too!
2. Research Attendee + Company
2. Research Attendee + Company
API calls are made to the OpenAI Responses API using the new web search preview endpoint. This allows us to search the web for any mentions of each attendee. If the email address is a company email, we also make a search request to find out about the company. We use some context about ourself (in the "Set Context" node) so that the LLM can make an educated guess if there are many people with the same name.
3. Generate + Send Report
3. Generate + Send Report
Finally, we combine all the data from the meeting attendees into a report. The report gets written in Markdown, converted into HTML, and the send via the Gmail API.
Edit Here
Edit Here
Edit a few variables here to get started:
- context: Some information about you to help the web search return the right people.
- email: The email that you want to send the report to.
http request and receive google calendar events and filter out myself
http request and receive google calendar events and filter out myself
Purpose and structure
This folder contains the http request and receive google calendar events and filter out myself workflow. Its executable nodes use aggregate, filter, gmail, googleCalendarTrigger, httpRequest, if, markdown, set, splitInBatches, splitOut. 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
Google Calendar Trigger
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/Splitout/0899_Splitout_GoogleCalendar_Update_Webhook.json MIT; preserve source notices.