Post LinkedIn Pages reports to Microsoft Teams
LinkedIn Pages follower gains, organic and paid, once a week. LinkedIn Pages goes into your data warehouse first, is linked there by SQL keys, and only then reaches Microsoft Teams. Colleagues read the answer in Teams, not an export of the source.
LinkedIn PagesConnectedFollower Statist…Time-Bound Follo…
Microsoft TeamsOrgan…TimeTimeDaily 09:00Paid follower growth on LinkedIn Pages reads as brand interest in Microsoft Teams unless someone splits it from organic.
Paste this into your AI assistant. It joins LinkedIn Pages follower segments and gains into one Data Mart in your data warehouse and posts the weekly organic and paid split to the Microsoft Teams channel.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /connectors/linkedin-pages-insights-to-microsoft-teams.md. The task: post a weekly LinkedIn Pages report to our Microsoft Teams channel with organic versus paid follower gain and the top follower industries, with a short note on the change. Tag the links you give me with utm_campaign=ai-task and utm_term=data-foundation. Use what you know about my context and goals
LinkedIn Pages Endpoints
2 LinkedIn Pages endpoints you can import. Each lands in its own table in your data warehouse.
Why LinkedIn Pages does not post straight to Microsoft Teams
LinkedIn Pages counts followers of your company page, not clicks or deals. A message posted from the page data shows how many people followed, and says nothing about the campaigns that earned them or the visits that came next. A Teams channel is read by people outside the team that built the report, so every number needs to explain itself. The join belongs in a warehouse first.
- LinkedIn Pages counts organic and paid followers, apart from campaign results
- A Teams channel reaches colleagues who never saw the source, so definitions must travel with the figures
- The data analyst links the sources by SQL keys and controls what the message says
LinkedIn PagesOrganic followersMicrosoft Tea…
Data warehouseJoined by idStep 1: Load LinkedIn Pages into your data warehouse first
Create a Data Mart with LinkedIn Pages as the source and choose where the data lands. It works with any popular data warehouse.
- Two endpoints and 18 fields to choose from, each endpoint in its own table
- Lifetime counts by seniority, industry, function and geography, plus gains by period
- Open the LinkedIn Pages connector for your data warehouse below
LinkedIn Pa…Data MartGoogle BigQuery
AWS Athena
Snowflake
AWS Redshift
Databrickslinkedin_pages.follower_stati…Step 2: Link LinkedIn Pages follower data into one Data Mart
In your data warehouse the model joins follower segments and follower gains by the page, organization_urn, into one Data Mart. Add your ad platforms in the same data warehouse to see what the paid gains cost.
- Both endpoints join on organization_urn
- Lifetime segments and gains per period read as one table
- Paid follower gains sit ready to meet ad spend
Step 3: Post LinkedIn Pages reports to a Teams channel
Create a Microsoft Teams destination in OWOX with the email address of the channel, taken from the channel menu in Teams, then add a report to the published Data Mart. Write the message in Markdown and check it in Preview.
- Every Teams channel can receive email, and OWOX sends the report to that address
- Type / to place the Time-Bound Follower Statistics table: time_range_start, time_range_end, organic_follower_gain, paid_follower_gain and the number of rows you pick
- Create & Run posts the first report straight away
Microsoft TeamsWeeklyLinkedIn Pages follower digesttime_range_starttime_range_endorganic_followe…paid_follower_g…Step 4: Put a short analysis under the LinkedIn Pages table in Teams
Add two or three lines beneath the table in the same message. Pick a send condition on the report, and open the Triggers tab to set the day and time of the run.
- The lines rest on time_range_end and organic_follower_gain from the table above them
- Figures come from a fresh run of the Data Mart before each message
- Send always, only when empty or only when not empty: chosen per report
Microsoft TeamsLinkedIn Pages follower digesttime_range_starttime_range_endorganic_followe…paid_follower_g…AnalysisRead organic_follower_gain and paid_follower_gain side by sideA week with only paid gains means growth depends on spendtime_range_end closes each period that time_range_start opensStep 5: Reuse LinkedIn Pages inside OWOX MCP
The same Data Mart works in OWOX MCP, your assistant for data. Request any report, chat with your data, then get it in Google Sheets or Excel in one click.
- Ask in plain words; the answer comes from your data warehouse
- Define the numbers once and every report reads them
Google SheetsOpen
ExcelOpen
- 0.41.0Rotating a connector key is one change: Sources share reusable Credentials
- 0.39.0Reload a year of history in one backfill, not twelve
- 0.37.0Clearer connector errors, and custom connectors that handle more APIs
- 0.36.0Start a connector run without expanding the Input Source card
- 0.35.0Resume an interrupted manual backfill from the last fully loaded date
Why OWOX for LinkedIn Pages in Microsoft Teams
Hand-built flows that read LinkedIn Pages and post to Teams carry the source's numbers only. OWOX posts the answers your data warehouse calculated, to the channel of your choice.
- Page growth for the comms team. Teams shows organic and paid follower gains where your comms and marketing teams already talk.
- You own the data. LinkedIn Pages lands in your own data warehouse, in tables you control, before anything reaches Teams.
- Nothing to build in Teams. The channel email address is all it needs: no custom connector, no flow to maintain on the Microsoft side.
- A message with a condition. Each report has its own send condition, so a Teams channel hears only when there is something to say.
- Maintained for you. When the source changes, the connector is updated; your Teams channel keeps getting the report.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.