Send Channel Message with Microsoft Teams API on New Survey Response from Survser API

Pipedream makes it easy to connect APIs for Microsoft Teams, Survser and 2,400+ other apps remarkably fast.

Trigger workflow on

New Survey Response from the Survser API

Next, do this

Send Channel Message with the Microsoft Teams API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Survser trigger and Microsoft Teams action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Survey Response trigger
1. Connect your Survser account
2. Configure timer
3. Select a Survey ID
Configure the Send Channel Message action
1. Connect your Microsoft Teams account
2. Select a Team
3. Select a Channel
4. Configure Message
5. Optional- Select a Content Type
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Survey Response on Survser

Description:Emit new event when a new survey response is received. [See the documentation](https://docs.survser.com/docs/api)

Version:0.0.1

Key:survser-new-survey-response

View on GitHub

Survser Overview#

The Survser API is designed to streamline survey management and analysis, providing a set of tools to create, distribute, and analyze surveys. On Pipedream, you can automate survey distribution, sync responses with other data systems, and trigger actions based on survey outcomes. This enables seamless integration with other apps for advanced data processing, notifications, and more, enhancing decision-making processes and response times.

Trigger Code#

import survser from "../../survser.app.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
import sampleEmit from "./test-event.mjs";

export default {
  key: "survser-new-survey-response",
  name: "New Survey Response",
  description: "Emit new event when a new survey response is received. [See the documentation](https://docs.survser.com/docs/api)",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    survser,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    surveyId: {
      propDefinition: [
        survser,
        "surveyId",
      ],
    },
  },
  hooks: {
    async deploy() {
      await this.processEvents(25);
    },
  },
  methods: {
    _getLastCreated() {
      return this.db.get("lastCreated");
    },
    _setLastCreated(lastCreated) {
      this.db.set("lastCreated", lastCreated);
    },
    emitEvent(response) {
      const meta = this.generateMeta(response);
      this.$emit(response, meta);
    },
    generateMeta(response) {
      return {
        id: response.id,
        summary: `New Response for Survey: ${response.survey.name}`,
        ts: Date.parse(response.createdAt),
      };
    },
    async processEvents(max) {
      const lastCreated = this._getLastCreated();
      let responses = await this.survser.getSurveyResponses({
        params: {
          surveyId: this.surveyId,
        },
      });
      if (!responses?.length) {
        return;
      }
      if (max) {
        responses = responses.slice(-1 * max);
      }
      this._setLastCreated(Date.parse(responses[responses.length - 1].createdAt));
      for (const response of responses.reverse()) {
        const ts = Date.parse(response.createdAt);
        if (ts >= lastCreated) {
          this.emitEvent(response);
        } else {
          return;
        }
      }
    },
  },
  async run() {
    await this.processEvents();
  },
  sampleEmit,
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
Survser	`survser`	`app`	This component uses the Survser app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Survey ID	`surveyId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

Survser uses API keys for authentication. When you connect your Survser account, Pipedream securely stores the keys so you can easily authenticate to Survser APIs in both code and no-code steps.

About Survser#

Grow your Business with Customer Feedback. Popup-Surveys for E-Commerce and SaaS.

Action#

Send Channel Message on Microsoft Teams

Description:Send a message to a team's channel. [See the docs here](https://docs.microsoft.com/en-us/graph/api/channel-post-messages?view=graph-rest-1.0&tabs=http)

Version:0.0.6

Key:microsoft_teams-send-channel-message

View on GitHub

Microsoft Teams Overview#

The Microsoft Teams API on Pipedream allows you to automate tasks, streamline communication, and integrate with other services to enhance the functionality of Teams as a collaboration hub. With this API, you can send messages to channels, orchestrate complex workflows based on Teams events, and manage Teams' settings programmatically.

Action Code#

import microsoftTeams from "../../microsoft_teams.app.mjs";

export default {
  key: "microsoft_teams-send-channel-message",
  name: "Send Channel Message",
  description: "Send a message to a team&#39;s channel. [See the docs here](https://docs.microsoft.com/en-us/graph/api/channel-post-messages?view=graph-rest-1.0&tabs=http)",
  type: "action",
  version: "0.0.6",
  props: {
    microsoftTeams,
    teamId: {
      propDefinition: [
        microsoftTeams,
        "team",
      ],
    },
    channelId: {
      propDefinition: [
        microsoftTeams,
        "channel",
        ({ teamId }) => ({
          teamId,
        }),
      ],
    },
    message: {
      propDefinition: [
        microsoftTeams,
        "message",
      ],
    },
    contentType: {
      propDefinition: [
        microsoftTeams,
        "contentType",
      ],
    },
  },
  async run({ $ }) {
    const {
      teamId,
      channelId,
      message,
      contentType,
    } = this;

    const response =
      await this.microsoftTeams.sendChannelMessage({
        teamId,
        channelId,
        content: {
          body: {
            content: message,
            contentType,
          },
        },
      });

    $.export("$summary", `Successfully sent message to channel ${channelId}`);

    return response;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Microsoft Teams	`microsoftTeams`	`app`	This component uses the Microsoft Teams app.
Team	`teamId`	`string`	Select a value from the drop down menu.
Channel	`channelId`	`string`	Select a value from the drop down menu.
Message	`message`	`string`	Message to be sent
Content Type	`contentType`	`string`	Select a value from the drop down menu:`texthtml`

Action Authentication#

Microsoft Teams uses OAuth authentication. When you connect your Microsoft Teams account, Pipedream will open a popup window where you can sign into Microsoft Teams and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Microsoft Teams API.

Pipedream requests the following authorization scopes when you connect your account:

User.Reademailoffline_accessopenidprofileChat.ReadChat.ReadWriteChatMessage.SendChannel.ReadBasic.AllChannelMessage.SendTeam.ReadBasic.AllSchedule.Read.All