Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Microsoft Teams, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands.
All connector references · Connect an account · AI setup and shared results
Read the teams joined by the connected Microsoft user.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Microsoft Teams connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. Connect through the provider’s authorization screen. If setup is unavailable, ask your Twidget administrator to configure this connection. |
Result
Returns team objects in value. Only one provider response is read; no continuation input is exposed.
Example
Choose your Microsoft Teams Account and add List joined teams. This command needs no other settings beyond the inputs described above. These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Reconnect Microsoft if authorization expired. The connected work/school user needs team/channel access and delegated permission to send messages. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Read channels belonging to one Microsoft Team.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Microsoft Teams connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. Connect through the provider’s authorization screen. If setup is unavailable, ask your Twidget administrator to configure this connection. |
| Team | text | Required. Team ID, usually a UUID, from List joined teams. A display name cannot replace the ID. Twidget text limit: 8,192 characters; provider-specific limits may be lower. |
Result
Returns channel objects in value. Any additional provider pages are not automatically followed.
Example
Choose your Microsoft Teams Account and add List channels. Set Team = "11111111-1111-4111-8111-111111111111". These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Reconnect Microsoft if authorization expired. The connected work/school user needs team/channel access and delegated permission to send messages. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Post a plain text channel message as the connected Teams user.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Microsoft Teams connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. Connect through the provider’s authorization screen. If setup is unavailable, ask your Twidget administrator to configure this connection. |
| Team | text | Required. Team ID, usually a UUID, from List joined teams. A display name cannot replace the ID. Twidget text limit: 8,192 characters; provider-specific limits may be lower. |
| Channel | text | Required. Channel ID from List channels, such as 19:...@thread.tacv2. It must belong to Team. Twidget text limit: 8,192 characters; provider-specific limits may be lower. |
| Message | text | Required. Plain text to post. HTML, attachments and adaptive cards are not supported by this command. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
Result
Returns the created message with id and body. This requires delegated channel-message permission, not app-only migration access.
Example
Choose your Microsoft Teams Account and add Send channel message. Set Team = "11111111-1111-4111-8111-111111111111"; Channel = "19:demo-channel@thread.tacv2"; Message = "Hello from the demo workflow.". These are illustrative values: replace example IDs and addresses with your own permitted test values. An intended live run creates/changes data or sends a message; inspect its receipt before repeating it.
Errors and limits
Reconnect Microsoft if authorization expired. The connected work/school user needs team/channel access and delegated permission to send messages. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Isolated tests and live debugging do not call connected providers. Enable Use live data only when you intend to contact the account. Writes, messages and AI requests can change real data or incur provider charges. A successful connection check does not prove access to every action. These examples explain the command contract; they are not evidence of a completed live provider request.
Dropbox commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Dropbox, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All ...
Stripe commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Stripe, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All c...
Resend commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Resend, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All c...
SendGrid commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → SendGrid, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All...
Salesforce commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Salesforce, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [A...
