Skip to main content

Tutorial 9: Send Teams Message

Estimated time: 10 min.


Teams Messaging - Intro

Sending messages from PIPEFORCE to external systems is very easy when there is an API or webhook available. This tutorial will demonstrate that by sending a message to Office 365 / Teams.

1 - Create a webhook in Microsoft Teams

In the first step, you need to create a webhook in Teams, so we can send data to it. To do so, follow these steps:

  1. Login to your Office 365 account:

  2. Open the Teams app

  3. Navigate to Teams → Your Teams → Select the channel you want to send messages to → Connectors:

  4. In the upcoming list click Configure of Incoming Webhook:

  5. Give the webhook a meaningful name and then click Create:

  6. Copy the generated webhook url into your clipboard, then click Done:

2 - Send a message from a pipeline

  1. Login to the portal

  2. Navigate to LOW CODE → Workbench

  3. The ad-hoc pipeline editor is shown

  4. Copy and paste this content into the editor, and overwrite any existing data there by this:

    url: ""
    body: |
    "text": "This message was sent with PIPEFORCE."
  5. Replace the url param by the webhook url you have copied to clipboard before.

  6. As you can see, we set the url and the body for the HTTP message, which will be used by the command, in order to send it to the Teams webhook using the given url. Note the pipe | character of parameter body. This is specific to YAML and allows to define a multi-line value without additional “line encodings” or “escapes”. We can write a JSON string straight here.

  7. Click RUN.

  8. Done. After a few seconds, you should receive a new message in the Teams channel:

  9. If you want, you can persist this pipeline in an app to keep it for later use.


Report an Issue

Your help is needed!

In case you're missing something on this page, you found an error or you have an idea for improvement, please click here to create a new issue. Another way to contribute is, to click Edit this page below and directly add your changes in GitHub. Many thanks for your contribution in order to improve PIPEFORCE!