Stay aligned with automatic Cinode updates in your shared Teams channels.
The Microsoft Teams Integration posts Adaptive Cards from Cinode into the Teams channels your team already works in. It surfaces what matters — new contacts, expiring roles, upcoming starts, available consultants, and more — so your team can act without leaving Teams.
💡 Looking for private, per-user notifications about missing data on individual sales projects? That’s a separate integration called Pipeline Assistant. Read the article.
Overview
This integration is an add-on. 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, reach out to us.
What the integration does
The Teams integration delivers scheduled digest notifications and real-time alerts from Cinode into Microsoft Teams.
Each notification is sent as an Adaptive Card with a consistent layout, making it easy to scan, click, and act directly from Teams.
A key difference from Pipeline Assistant:
Teams Integration → shared channel notifications
Pipeline Assistant → private, per-user notifications
Notifications are configured at two levels:
Instance level (admin-controlled) → connections and schedules
User level (individual) → channels, filters, and preferences
Available notification flows
Flow | Description | Trigger |
Ending Roles | Consultant assignments ending within a defined timeframe | Scheduled |
Upcoming Roles | Open roles starting soon, filtered by Cinode team | Scheduled |
Expiring Certifications | Certifications approaching expiry across all profiles | Scheduled |
Due Tasks | Tasks/events that are coming due | Scheduled |
New Contacts | Contacts added recently | Scheduled |
Contacts without activity | Contacts not updated within a defined period (includes CSV export) | Scheduled |
Project updates | Recently won projects and projects nearing close date | Scheduled |
Updated Profiles | Consultant profiles updated recently | Scheduled |
Role Created | New role created with matching consultants | Real-time (event-driven) |
All scheduled flows default to disabled and must be enabled explicitly.
How it supports your sales process
Early signals — identify inactive contacts, expiring roles, and upcoming needs early
Less manual work — reduce time spent searching in Cinode
Shared visibility — keep teams aligned through shared channels
Flexible setup — each user chooses what to subscribe to
Example notifications
Cinode Market announcement — shared update posted to a Teams channel
Bench or availability overview — consultants with role, availability date, and profile link
Expiring roles digest — consultants ending assignments with project context
Prerequisites
To use the integration, you need:
A Cinode account with API access
A Microsoft Teams workspace
Admin rights to deploy integrations in Cinode
Access to Cinode’s Integration Portal
Configuration overview
The integration has five configuration areas:
Connections (instance level)
Schedules (instance level)
Teams team (user level)
Flows and Channels (user level)
Cinode settings (user level)
Set up the required connections:
Cinode Connection — API credentials (Static Token)
Microsoft Teams Connection — OAuth connection to your Teams workspace
1. Connections — instance level and 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.
Both must be authorised before continuing.
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.
2. Schedules — instance level
Each scheduled flow has its own schedule configured by an admin.
All flows default to Never (disabled).
Examples:
Ending Roles
Upcoming Roles
Expiring Certifications
Due Tasks
Contacts Added
Contacts without activity
Project updates
Profile updates
Additional setting:
Role Creation Sleep time — delay before processing a new role (default: 2 seconds)
Users can opt out of a flow by not assigning a channel.
3. Teams team — user level
Select which Microsoft Teams team to use.
This enables the channel picker used in the next step.
4. Flows and Channels — user level
Each user decides where notifications should be sent.
For every flow:
Select a Teams channel
Or leave empty (Not subscribed) to opt out
This allows:
Different users → different channels
Same flow → multiple channels across the organisation
5. Cinode settings — user level
These settings control filtering and matching logic per user.
Examples:
Cinode teams — filter roles by team
Future days — how far ahead to check for ending roles
Future days for starting roles — upcoming roles window
Days not touched — inactivity threshold for contacts
Days created contacts — how far back to include new contacts
Managers / Customers — filter contacts
Untouched profile days — inactive profiles
Match on location — enable geographic filtering
Location radius — distance for matching
Matching score — minimum score for role matching
Preliminary bookings — include/exclude partially staffed roles
Role Created — how matching works
When a new role is created in Cinode:
Booking check
If already booked → no notification (unless preliminary bookings allowed)
Location filtering
Applies radius if enabled
Stops if location missing and not allowed
Matching logic
Evaluates skills, availability, and score
Notification
Sends Adaptive Card with matching consultants
💡 If company address data changes, redeploy the integration to refresh matching data.
Choosing notification frequency
Each flow can be:
Real-time — triggered by events
Scheduled — based on configured cron (daily, weekly, custom)
Goal: stay informed without overwhelming the channel.
Troubleshooting
Issue | Possible cause | Solution |
No notifications | Schedule not enabled | Enable schedule at instance level |
No notifications (user) | No channel selected | Assign a channel in Flows and Channels |
Wrong channel | Incorrect mapping | Update channel selection |
Missing data | Incomplete Cinode data | Verify underlying records |
Wrong timezone | Not configured | Set correct timezone (e.g. Europe/Stockholm) |
FAQ
Why am I not receiving notifications?
Check:
Schedule is enabled
Channel is selected
Correct Teams team is chosen
Can different users use different channels?
Yes. Configuration is per user.
Can multiple flows go to the same channel?
Yes.
How does the CSV download for contacts work?
The Adaptive Card button triggers a webhook that generates and downloads the file.
How does Role Created handle booked roles?
Booked roles are skipped unless preliminary bookings are allowed.
What is Matching Score?
A 0–100 score from Cinode’s matching engine. Only consultants above the threshold are included.
Is Pipeline Assistant included?
No. It is a separate integration for private notifications.
Need help?
Contact your Customer Success Manager or email support@cinode.com.