Step 2: Connect Google Calendar and Initialize Inputs

Prepare the context and attendee list that the workflow will use for research prompts and delivery.

1. In Configure Inputs, set context to I am working in web development, based in Singapore/Australia, and I work with startups (edit as needed).
2. Set email to [YOUR_EMAIL] so the briefing is sent to you.
3. Set attendees to {{ $json.attendees }} to pass in the event attendee list.
4. Keep the Flowpast Branding node for reference; it’s a static note and does not affect execution.

Step 3: Set Up Attendee Processing

Split the attendees into individual items, exclude yourself, and prepare for iteration and conditional routing.

1. In Expand Attendee List, set Field To Split Out to =attendees.
2. In Exclude Self Attendee, keep the condition {{ $json.self }} set to false to remove your own address.
3. Use Iterate Attendees to batch process each attendee (leave defaults unless you want to limit batch size).
4. Note that Iterate Attendees outputs to both Aggregate Findings and Check Work Email in parallel, enabling accumulation while research runs.

Step 4: Set Up Research Queries and Routing

Build prompts for company and person research, then route based on whether the email appears to be a personal address.

1. In Check Work Email, keep the condition that checks {{ $('Iterate Attendees').item.json.email }} with notRegex against personal email domains.
2. In Build Company Query, set prompt to the full expression that builds a company lookup using {{ $('Iterate Attendees').item.json.email.split("@")[1] }} and {{ $('Configure Inputs').item.json.context }}.
3. In Company Research Request, set URL to https://api.openai.com/v1/responses, Request Method to POST, and Body Parameters JSON to {{ JSON.stringify({ model: "gpt-4o", tools: [{ type: "web_search_preview" }], input: $json.prompt }) }}.
4. Credential Required: Connect your httpHeaderAuth credentials in Company Research Request.
5. In Build Person Query, set prompt to the full expression that includes {{ $('Iterate Attendees').item.json.email }} and your context from {{ $('Configure Inputs').item.json.email }}.
6. In Person Research Request, mirror the same OpenAI request settings and body JSON as the company request.
7. Credential Required: Connect your httpHeaderAuth credentials in Person Research Request.

Step 5: Configure Output Assembly and Email Delivery

Combine research output, render the briefing in HTML, and email it to the configured recipient.

1. In Assemble Output Fields, map person to {{ $json.output[1].content[0].text }}, company to the conditional expression referencing Company Research Request, and email to {{ $('Iterate Attendees').item.json.email }}.
2. In Aggregate Findings, set Aggregate to aggregateAllItemData to collect all attendee results.
3. In Render HTML Summary, set Mode to markdownToHtml and use the provided markdown expression for the briefing.
4. In Email Briefing, set Send To to {{ $('Configure Inputs').item.json.email }}, Message to {{ $json.data }}, and Subject to Meeting Briefing: {{ $('Calendar Event Watcher').item.json.summary }} ({{ new Date($('Calendar Event Watcher').item.json.start.dateTime).format("dd/MM/yyyy") }}).
5. Credential Required: Connect your gmailOAuth2 credentials in Email Briefing.

Step 6: Test and Activate Your Workflow

Run a manual test to confirm the workflow generates and emails the briefing, then activate it for ongoing use.

1. Click Execute Workflow and create a new calendar event with at least one attendee.
2. Confirm that Calendar Event Watcher triggers and that Render HTML Summary produces HTML output.
3. Check your inbox to verify that Email Briefing sends a message with the expected subject and content.
4. Activate the workflow using the Active toggle once the test succeeds.