Automate Daily Meeting Social Briefs with n8n

Picture this: it is 8:55 a.m., your meeting starts in five minutes, and you are frantically opening LinkedIn and Twitter in 17 different tabs trying to figure out what your prospect has been posting lately. By the time you find their latest update, the call has already started and you are still reading their tweet from last month.

Or, alternative universe: you open your inbox, sip your coffee, and there is a neat little email waiting for you that already lists the latest LinkedIn posts and tweets from every company you are meeting today. No tab chaos, no panic. Just instant context.

This n8n workflow template gives you the second universe. It automatically collects social media activity for your meeting attendees, turns it into a clean HTML email, and sends it to you before your day gets going. Your meetings stay smart and your mornings stay calm.

What this n8n workflow actually does (in plain English)

At its core, this is a social media briefing bot for your calendar. Here is what the workflow handles for you:

• Runs automatically every morning at 07:00 with a Schedule Trigger.
• Checks your Google Calendar for all events happening that day.
• Pulls out attendee email domains and enriches them via Clearbit to find company names and social profiles.
• Uses RapidAPI to grab recent LinkedIn posts and tweets from those companies.
• Wraps the posts in a nicely formatted HTML email, per company.
• Sends that email to a predefined list of recipients using the Gmail node with OAuth2.

Translation: less time stalking people on social media, more time pretending you always knew what they were up to.

Why this automation is worth your 10 minutes of setup

This workflow is especially handy for sales teams, account managers, founders, and executives who need to sound informed without spending half the morning researching. Instead of:

• Manually opening LinkedIn and Twitter for every meeting attendee,
• Guessing which company profile is the right one,
• Skimming endless feeds to find anything remotely relevant,

you get a curated, data-driven briefing delivered straight to your inbox each morning. That means:

• Faster meeting prep.
• Better questions and talking points.
• Less repetitive research that slowly drains your will to work.

Before you start: keys, tools, and accounts you need

To get this n8n workflow up and running, you will need a few accounts and API keys ready:

RapidAPI subscriptions

On RapidAPI, register and subscribe to:

• Fresh LinkedIn Profile Data (for LinkedIn company posts, endpoint get-company-posts)
• Twitter (twitter154) (for company tweets, endpoint for user tweets)

Other required credentials

• Clearbit API key for company enrichment.
• Google Calendar credentials configured in n8n.
• Gmail OAuth2 credentials configured in n8n for sending the emails.

You will store the RapidAPI keys and recipient email addresses in a dedicated Set node called Setup inside the workflow.

How the workflow works, step by step

Let us walk through what happens under the hood once the workflow kicks off at 07:00. You only set this up once, then it quietly does the boring work for you every day.

1. Start with a daily Schedule Trigger

The workflow begins with a Schedule Trigger node. It is configured to run once a day at 07:00, which is early enough to prepare you for most morning meetings without requiring you to be awake at an unreasonable hour.

2. Configure the “Setup” node

Next comes a Set node named Setup. Think of it as the control center for:

• Your RapidAPI keys for LinkedIn and Twitter.
• The list of recipient email addresses who should receive the daily digest.

This keeps your configuration tidy and makes it easy to change recipients or rotate keys later without hunting through multiple nodes.

3. Pull today’s meetings from Google Calendar

The workflow then queries your Google Calendar for events that fall within the current day. It uses:

• timeMin and timeMax set to today,
• singleEvents enabled so that recurring meetings appear as separate instances.

This gives you a clear list of today’s meetings to work with.

4. Extract attendee domains from email addresses

Next, a Set node processes each event and pulls out the attendees’ email addresses. For each email, it extracts the domain, which is everything after the @ symbol.

This domain is used as a proxy for the company, which makes it easier to:

• Group attendees by organization,
• Enrich the company using Clearbit,
• Fetch the right social accounts later on.

5. Split and filter the events

To handle each domain on its own, the workflow uses a Split Out node. This lets n8n process every domain individually rather than as one big blob of data.

After that, a Filter node removes any entries that do not have a valid domain. That way you are not wasting API calls on incomplete or irrelevant data.

6. Enrich each company with Clearbit

With clean domains in hand, the workflow calls Clearbit’s Enrichment API. For each domain, Clearbit returns handy company details like:

• Company name,
• Likely LinkedIn profile,
• Twitter handle and other social links,
• Extra context that can inform your meeting.

These enrichment results feed into the next step, where the workflow decides which social networks to query.

7. Decide what to fetch with a Switch node

A Switch node then looks at the Clearbit data and routes each company down the right path:

• If a LinkedIn handle is present, it sends the company to the LinkedIn RapidAPI branch.
• If a Twitter account or ID is available (either from Clearbit or the original calendar event), it sends the company to the Twitter RapidAPI branch.
• If both exist, both branches can run in parallel so you get a fuller picture.

You get maximum coverage without manually checking which company is on which platform.

8. Fetch the latest posts using RapidAPI

Two HTTP Request nodes are responsible for talking to RapidAPI:

• Fresh LinkedIn Profile Data with the get-company-posts endpoint.
• Twitter API via twitter154 to fetch recent user tweets.

In both cases, you must include:

• X-RapidAPI-Host header,
• X-RapidAPI-Key header.

Make sure you respect the rate limits documented by RapidAPI. Your future self will thank you when nothing randomly breaks at 7:01 a.m.

9. Turn raw posts into readable HTML

Once the posts come back, Code nodes step in as your formatting assistants. They:

• Build simple HTML tables for LinkedIn posts and tweets,
• Include post text and links,
• Add basic reaction counters like likes, comments, and retweets for quick context.

The result is a compact, scannable layout that looks good in an email and does not require you to open each social network unless you really want to.

10. Merge everything and prepare the email body

A Merge node then combines the LinkedIn and Twitter data for each company so you get a unified view per organization.

After merging, a Set node:

• Pulls in the attendee email,
• Includes the meeting time,
• Collects all the formatted HTML snippets.

This data is then passed into an HTML node, which assembles the final HTML email body that will land in your inbox.

11. Send the briefing with Gmail

Finally, a Gmail node uses your OAuth2 credentials to send the generated HTML email to the recipient list defined in the Setup node.

You can send it to yourself, your team, or anyone else who needs a quick social briefing before hopping into calls.

Troubleshooting and best practices

Handle rate limits and batching gracefully

Both RapidAPI and Clearbit enforce rate limits. To avoid angry APIs:

• Use the HTTP Request node’s batching options where appropriate.
• Add small delays between requests to stay under the limit.
• For high-volume calendars, consider staggering workflow runs or queuing requests.

The provided template already uses modest batching and delay settings, which you can tune based on your usage.

Privacy and compliance reminders

As fun as enrichment data can be, it comes with responsibilities:

• Only enrich and contact companies you are allowed to research.
• Do not send sensitive calendar or attendee data to third parties if it violates your organization’s policies.
• Review internal compliance guidelines before rolling this out broadly.

Build in error handling

APIs sometimes fail, tokens expire, and networks have bad days. To avoid silent breakage:

• Add error triggers or an IF fallback branch to catch failed API calls.
• Send yourself a Slack or email alert when enrichment or social fetches fail.
• Log unexpected responses in temporary nodes while you debug.

Testing tips before going fully automatic

1. Run the workflow manually with a sample calendar event to confirm credentials and formatting.
2. Open the resulting HTML email in multiple email clients to check that everything renders nicely.
3. During development, log full API responses in extra nodes so you can inspect raw data and adjust your mapping if needed.

How to extend and customize the workflow

This template is intentionally modular, so you can customize it instead of building from scratch. A few ideas:

• Add more social platforms found by Clearbit, such as Facebook, Instagram, or GitHub, by creating additional HTTP Request nodes plus formatting branches, then merging their outputs.
• Highlight sentiment or keywords by aggregating mentions of specific topics or tracking basic sentiment for a quick at-a-glance summary.
• Pull in news mentions using a news API so you see both social posts and press coverage in one email.
• Create Slack or Microsoft Teams summaries in parallel with the email for teams that live in chat apps.

The core flow stays the same, you just bolt on extra branches where you need more context.

Security tips for a safe setup

Since this workflow touches multiple APIs and a Gmail account, keep things locked down:

• Store API keys as credentials in n8n or as environment variables, not hardcoded in nodes.
• Limit the scope of the Gmail account used to send emails and monitor access to it.
• Rotate API keys periodically.
• Follow least-privilege principles for service accounts and credentials.

Wrap-up: from tedious research to automatic briefings

With a few API keys and this n8n workflow template, you can turn meeting prep from a repetitive scavenger hunt into a calm, automated ritual. Instead of doom-scrolling through company feeds before every call, you get a concise social briefing delivered to your inbox each morning.

Import the template, plug in your RapidAPI and Clearbit keys in the Setup node, connect Google Calendar and Gmail, then run a manual test with a sample event. Once it looks good, let the Schedule Trigger take over and enjoy the extra time back in your day.

Ready to try it? Import the workflow into n8n, configure your credentials, and see your first daily social digest land in your inbox. If you want to adapt it for your team with extras like Slack alerts, CRM links, or sentiment highlights, you can easily extend the existing nodes and branches or share it with your automation-savvy colleague to tweak further.