Microsoft Teams Notifications - NEW

Stay aligned with automatic Cinode updates in your shared Teams channels

The Microsoft Teams Notifications integration posts Adaptive Cards from Cinode directly into the shared Teams channels your team already works in. It surfaces the things that matter — new contacts, expiring roles, upcoming starts, bench availability, and more — so your team can act on them without leaving Teams.

💡 Looking for private, per-user notifications about missing data on individual sales projects? That's a separate integration called Pipeline Assistant. See the Pipeline Assistant article.

Overview

This integration is an add-on. Please contact your Customer Success Manager (CSM) or Cinode Support to activate it.

🔒 To set up the integration, you need one of the following Cinode permission levels: Partner Manager, Manager, Recruiter, or Admin.

💡 All integrations in Cinode are configurable. If you need a notification flow that is not listed below, let us know.

What the integration does

Microsoft Teams Notifications delivers scheduled or event-driven updates from Cinode to the shared Teams channels you choose. Each notification is rendered as an Adaptive Card using a consistent layout, so your team can scan, click, and act directly from Teams.

Notifications are configured at instance level by an admin and posted to channels the whole team can see — this is the key difference from the Pipeline Assistant, which sends private notifications per user.

Available notification flows

Flow	Description	Typical recipients
Public Announcements (Cinode Market)	Shares company-wide announcements from Cinode Market.	Everyone who should see Cinode Market updates — sales, delivery, leadership.
Contacts Added	Lists contacts added within a selected time range.	Sales/BD teams, recruiters monitoring new relationships.
Untouched Contacts	Lists contacts that haven't been contacted within a configured number of days. Includes a secure one-time download link for an Excel export.	Sales/BD reps, Partner/Account Managers.
Upcoming Roles Starting	Digest of users booked on roles starting within a configured future window.	Resource and Delivery managers.
Expiring Roles	Digest of booked users on roles ending within a configured future window.	Resource managers, project owners.
New Role Matching	Event-driven. When a Role Matching request is created or updated, ranked candidates are posted to Teams based on availability, skills, languages, locations, and teams.	Sales, resourcing, recruiters.
Due Tasks	Lists Cinode tasks due within the next 24 hours.	Anyone using tasks for follow-ups.
Updated Profiles	Detects employee profiles updated within a configured window.	Sales and recruitment teams acting on fresh profile data.
Bench List Weekly Digest	Weekly summary of users currently available on the bench.	Resource managers, sales, leadership.

Each flow either runs on a configurable schedule (daily / weekly / custom cron) or is triggered by an event in Cinode (webhook). You decide which flows to enable for your organisation.

How it supports your sales process

Early signals — catch inactive contacts, expiring roles, and upcoming starts before they become urgent.
Fewer manual checks — let Teams deliver what would otherwise require digging through Cinode.
Shared visibility — everyone in the channel sees the same information at the same time.
Flexible cadence — pick real-time, daily, or weekly per flow.

Example notifications

Cinode Market announcement — a public update posted to a shared Teams channel for company-wide visibility.

Bench list weekly digest — a scheduled Adaptive Card listing available consultants, each entry showing name, role, availability date, and a link to the consultant's Cinode profile.

Expiring roles digest — booked users on roles ending within the configured window, enriched with customer and project info.

(Keep the existing screenshots from the current articles — the Cinode Market example and the "available consultants in your Cinode team" example fit well here.)

Prerequisites

To use the Microsoft Teams Notifications integration, you need:

A Cinode account with API access
A Microsoft Teams connection authorised for your organisation
Access to Cinode's Integration Portal (sent to you after sign-up)
Activation by your Customer Success Manager

Setting up the integration

The integration is configured in Cinode's Integration Portal. Configuration is done once at instance level by an admin.

Step 1 — Open the Integration Portal

Log in to flows.cinode.com. You'll get access by reaching out to your CSM.
Go to Marketplace and find the Teams integration.
Click Configure.

Step 2 — Connect Cinode and Microsoft Teams

Under Configuration, link:

Cinode Connection — add a Static Token from Cinode. See Cinode REST API for how to create one.
Microsoft Teams Connection — authorise Cinode to post messages to your Teams workspace.

Make sure both connections are authorised successfully before continuing.

Step 3 — Choose which flows to activate

Enable the notification flows that your team needs, for example:

Contacts Added
Expiring Roles
Upcoming Roles Starting
Bench List Weekly Digest

You can enable or disable flows later as your needs change.

Step 4 — Set schedules

Define how often each scheduled flow should run. For example:

Contacts Added → every Monday at 08:00
Expiring Roles → every Friday at 10:00
Bench List Weekly Digest → every Monday at 07:00

Event-driven flows (like New Role Matching) don't need a schedule — they fire automatically when the triggering event happens in Cinode.

Step 5 — Assign Teams and channels

For each active flow, select the Teams team and channel where the Adaptive Cards should be posted. Different flows can post to different channels if that suits your workflow better.

Step 6 — User Level Configuration

After the general configuration is done, add a User Level Configuration. This tells the integration which Cinode users should be included in flows that filter by owner (such as Untouched Contacts, which can be filtered by Managers and Customers).

Step 7 — Verify and test

Save and publish your configuration.
Trigger a flow to test — for example, add a new contact in Cinode, or wait for the next scheduled run.
Confirm the Adaptive Card arrives in the expected Teams channel.

Choose when you receive notifications

Each flow can be set to:

Real-time — event-driven flows fire as soon as something happens in Cinode
Daily — a once-per-day digest
Weekly — a summary once a week

Pick the cadence that fits each flow. The goal is to stay informed without overloading the channel.

Troubleshooting

Issue	Possible cause	Solution
No notifications in Teams	Teams Connection missing or invalid	Reconnect Microsoft Teams in the Integration Portal
Notifications going to the wrong channel	Wrong Team/Channel selected for that flow	Update the Team and Channel selection for the affected flow
Data missing from messages	Required Cinode data not populated	Check that the underlying records in Cinode have the expected fields
Wrong timezone for scheduled runs	No timezone set in configuration	Set the `timeZone` field to your local zone (e.g. `Europe/Stockholm`)