Summary
A Microsoft Teams message can be posted from an iPaaS.com message record through Manual Sync or automatic outbound delivery. Each transfer creates one new message in a Teams channel or chat. The message body is delivered as formatted (HTML) content, with an optional subject.
ID Format
Manual Sync ID Format. On the iPaaS.com Manual Sync page, enter the iPaaS.com-side message record ID (for example, 381443).
External ID Format. After a message is posted, Microsoft Teams returns the new message identifier, which iPaaS.com records as the external ID that links the iPaaS.com record to the Teams message (for example, 1612289992105). This identifier is unique within a given channel.
Deleted Record Support
Outbound delete is not supported. Deleting a record in iPaaS.com does not remove a message from Microsoft Teams, and delete mappings are not included in the default templates.
Custom Field Support
Custom fields are not supported for this collection.
Mapping Collection Status
Status: Enabled. The collection has no mapping filter, so every dispatched message record is processed.
Trigger Events: Manual Sync (always available), and automatic delivery on message Add and Update events once the subscriber enables the corresponding outbound triggers under Outbound Data Flows.
Duplicate or Conflicting Mappings
There are no other mapping collections that post messages for this integration, and collision handling does not apply to this collection.
Supported Child Collections
None. This is a standalone collection with no child collections.
System Caveats
Microsoft Teams Caveats
The destination team is fixed by the Teams Group ID subscription setting. To post to a different team, update that setting.
The destination channel must already exist in the team. The integration does not create channels.
The message body is posted as HTML, so basic formatting in the content is preserved.
Microsoft Teams enforces its own request limits. Use the subscription's throttle settings to pace outbound requests.
iPaaS.com Caveats
Message content must be available. Content is assembled from the message text and its supporting detail; if the text or supporting detail is missing, no content is produced and the message is not sent.
Setup Requirements
Complete the Microsoft Teams OAuth connection (see the Microsoft Teams Installation Instructions).
Set the Teams Group ID subscription setting to the team that owns the destination channel.
Set the destination channel name in the channel mapping (replace the shipped TestChannel placeholder), or map a chat instead (see the Mappings section below).
To enable automatic delivery, subscribe to the relevant message Add and Update triggers under Outbound Data Flows.
Integration Flow
A message record is dispatched from iPaaS.com (through Manual Sync or an enabled outbound trigger).
The integration resolves the destination — a channel (by name, within the configured team) or a chat.
The message content and optional subject are assembled.
The integration posts a new message to the resolved channel or chat in Microsoft Teams.
Microsoft Teams returns the new message identifier, which iPaaS.com stores as the external ID.
Mappings
Add/Update Microsoft Teams Channel Message FROM iPaaS.com
iPaaS.com data type: Message
Description. Posts a new message to a Microsoft Teams channel or chat from an iPaaS.com message record.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Teams) | Description |
Dynamic Formula |
| ChannelId | Required (a destination is required — channel or chat). Resolves the destination channel by display name within the configured team; the match is not case-sensitive. TestChannel is a placeholder to replace with your channel's display name. If the named channel is not found, the message posts to the first channel in the team. |
Dynamic Formula |
| Content | Required. Builds the message body from the message text and its supporting detail. When the inputs are not available, the formula returns |
Field | Text | Subject | Optional. Uses the message text as the message subject. Leaving it unmapped posts the message without a subject. |
Posting to a chat instead of a channel. To deliver the message to a chat rather than a channel, remove the ChannelId mapping and add a mapping to ChatId instead. Only one destination is supported — if both a channel and a chat are provided, the message is not sent and an error is recorded.
To obtain a chat ID, open the chat in the Microsoft Teams web app and copy the chat identifier from the page URL. A chat ID has the form 19:<identifier>@thread.v2 — for example, 19:2da4c29f6d7041eca70b638b43d45437@thread.v2. A simple way to map it is a Static mapping:
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Teams) | Description |
Static |
| ChatId | Required when posting to a chat. The identifier of the chat to post to, copied from the chat's URL in the Microsoft Teams web app. Replace the example value with your own chat ID. When posting to a chat, the subject is shown in bold at the top of the message body. |
Error Handling
For the errors this flow can produce and how to resolve them, see the Microsoft Teams Error Messages article. The most common are a missing destination (no channel or chat resolved), both a channel and a chat provided, and missing message content.
Testing & Validation
Test Scenarios
Sync a message record with a valid channel name and confirm the message appears in the target Teams channel.
Map a chat ID instead of a channel and confirm the message appears in the target chat with the subject shown in bold.
Attempt a sync with no resolvable channel or chat and confirm the expected error appears in the iPaaS.com Error Logs.
Manually sync using the documented ID format and confirm success.
Validation Checklist
The Teams Group ID setting points to the correct team.
The channel name in the mapping matches an existing channel exactly.
Message content is produced (the message has text and supporting detail).
The external ID is recorded after a successful sync.
Additional Notes
This collection delivers messages outbound only; it does not update previously posted messages, delete messages, or read messages from Microsoft Teams. See the Microsoft Teams Integration Known Limitations article for details.