Microsoft Teams
Manage Teams messages from Era and workflows and direct team updates to the correct channel or chat.
Manage Teams messages from Era and workflows and direct team updates to the correct channel or chat.
Where to use it
On the web, Settings → Apps → Installed apps (/settings/apps) manages connections; Apps (/apps) adds them. In Era Desktop: Business → Apps and Settings → Apps → Installed apps.
What you need
| Field | What to supply |
|---|---|
| Hesap girişi / Account sign-in | Sign in at the provider and grant access; do not paste an account password into Era |
Connect step by step
Open the catalog
Find Microsoft Teams in Apps (/apps).
Complete authorization
Use Connect account to grant provider access, or enter the required key in the connection form.
Choose the right account
Choose the account under Settings → Apps → In my chats with Era. Workflows and Era agents select their own accounts separately.
Try one operation
Check access with a read or draft operation first. Explicitly choose the workflow target and connection and inspect the run result.
Era and workflow actions
These are actions declared by the existing workflow block. Select the connected account and each action’s target IDs; listing an action does not run it automatically.
Triggers
| Trigger | When it starts |
|---|---|
microsoftteams_webhook | Trigger workflow from Microsoft Teams channel messages via outgoing webhooks |
Permissions and limits
Before connecting
Some Microsoft scopes need administrator consent. Channel message and chat subscription are separate triggers. A Teams connection does not create a support Inbox channel.
Apps read permission shows accounts; manage changes connections/settings; delete removes them. Inbox channel management needs Inbox manage, and payment settings need Finance manage. Workflows and Era also obey the target module’s permissions.
Related modules
Ask Era
Show recent messages in the selected Teams chat.
Specify the account and target record. Era uses the connected account’s access and your role permissions; an example prompt is not a completed operation.
For technical teams
The connection flow depends on these platform configuration names; never put their values in user documentation: MICROSOFT_CLIENT_ID, MICROSOFT_CLIENT_SECRET.
Code sources: apps/studio/lib/integrations/definitions.ts, apps/studio/app/(app)/apps/components/connect-app.tsx, apps/studio/blocks/blocks/microsoft_teams.ts, packages/os-kernel/src/integrations/catalog.ts.