Send Reaction with LoopMessage API on Ticket Solved (Instant) from Zendesk API

Pipedream makes it easy to connect APIs for LoopMessage, Zendesk and 2,400+ other apps remarkably fast.

Trigger workflow on

Ticket Solved (Instant) from the Zendesk API

Next, do this

Send Reaction with the LoopMessage 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 Zendesk trigger and LoopMessage action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the Ticket Solved (Instant) trigger
1. Connect your Zendesk account
2. Select a Trigger Category ID
3. Optional- Configure Custom Subdomain
4. Optional- Select one or more Fields
5. Optional- Configure JSON Body
Configure the Send Reaction action
1. Connect your LoopMessage account
2. Configure Recipient
3. Configure Text
4. Optional- Configure Sender Name
5. Optional- Configure Status Callback
6. Optional- Configure Status Callback Header
7. Configure Message ID
8. Select a Reaction
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#

Ticket Solved (Instant) on Zendesk

Description:Emit new event when a ticket has changed to solved status

Version:0.2.2

Key:zendesk-ticket-solved

View on GitHub

Zendesk Overview#

The Zendesk API enables seamless integration of Zendesk's customer service platform with your existing business processes and third-party applications. By leveraging this API with Pipedream, you can automate ticket tracking, sync customer data, escalate issues, and streamline communication across multiple channels. This can significantly increase efficiency, accelerate response times, and enhance the overall customer experience. Automations can range from simple notifications to complex workflows involving data transformation and multi-step actions across various services.

Trigger Code#

import common from "../common/ticket.mjs";

export default {
  ...common,
  name: "Ticket Solved (Instant)",
  key: "zendesk-ticket-solved",
  type: "source",
  description: "Emit new event when a ticket has changed to solved status",
  version: "0.2.2",
  dedupe: "unique",
  methods: {
    ...common.methods,
    getWebhookName() {
      return "Ticket Solved Webhook";
    },
    getTriggerTitle() {
      return "Ticket Solved Trigger";
    },
    getTriggerConditions() {
      return {
        all: [
          {
            field: "update_type",
            value: "Change",
          },
          {
            field: "status",
            operator: "value",
            value: "solved",
          },
        ],
      };
    },
  },
};

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
Zendesk	`app`	`app`	This component uses the Zendesk app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
N/A	`http`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
Trigger Category ID	`categoryId`	`string`	Select a value from the drop down menu.
Custom Subdomain	`customSubdomain`	`string`	For Enterprise Zendesk accounts: optionally specify the subdomain to use. This will override the subdomain that was provided when connecting your Zendesk account to Pipedream. For example, if you Zendesk URL is https://examplehelp.zendesk.com, your subdomain is `examplehelp`
Fields	`fields`	`string[]`	Select a value from the drop down menu.
JSON Body	`jsonBody`	`string`	Custom JSON Body of the incoming payload. Setting `jsonBody` will overwrite the `fields` prop

Trigger Authentication#

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

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

triggers:writewebhooks:writereadtickets:writetickets:readusers:writeorganizations:readorganizations:write

About Zendesk#

Zendesk is award-winning customer service software trusted by 200K+ customers. Make customers happy via text, mobile, phone, email, live chat, social media.

Action#

Send Reaction on LoopMessage

Description:Action to submit your request to the sending queue. When a request in the queue will be ready to send a reaction in iMessage, an attempt will be made to deliver it to the recipient. [See the documentation](https://docs.loopmessage.com/imessage-conversation-api/messaging/send-message#send-reaction)

Version:0.0.2

Key:loopmessage-send-reaction

View on GitHub

LoopMessage Overview#

The LoopMessage API offers you the ability to send, receive, and manage messages within your applications. Through Pipedream's integration, you can harness this API to automate communication processes, organize message flows, and even connect to various data sources or other APIs to create complex messaging workflows. With Pipedream, you can trigger actions based on events, schedule messages, and interact with users in real-time without managing servers or infrastructure.

Action Code#

import common from "../common/send-message.mjs";
import constants from "../../common/constants.mjs";

export default {
  ...common,
  key: "loopmessage-send-reaction",
  name: "Send Reaction",
  description: "Action to submit your request to the sending queue. When a request in the queue will be ready to send a reaction in iMessage, an attempt will be made to deliver it to the recipient. [See the documentation](https://docs.loopmessage.com/imessage-conversation-api/messaging/send-message#send-reaction)",
  type: "action",
  version: "0.0.2",
  props: {
    ...common.props,
    messageId: {
      type: "string",
      label: "Message ID",
      description: "The ID of the message to react to. You can get it from the webhook trigger.",
    },
    reaction: {
      type: "string",
      label: "Reaction",
      description: "Reactions that starts with `-` mean *remove* it from the message. You can check the [Apple guide](https://support.apple.com/HT206894) about reactions and tapbacks.",
      options: constants.REACTIONS,
    },
  },
  methods: {
    ...common.methods,
    getSummary(response) {
      return `Successfully sent a reaction to with ID \`${response.message_id}\``;
    },
  },
};

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
LoopMessage	`app`	`app`	This component uses the LoopMessage app.
Recipient	`recipient`	`string`	The recipient of the message. This can be a phone number or email address.
Text	`text`	`string`	The text of the message.
Sender Name	`senderName`	`string`	Your dedicated sender name. This parameter will be ignored if you send a request to a recipient who is added as a Sandbox contact. If you've connected a phone number, you'll need to keep passing your original sender name. DON'T use a phone number as a value for this parameter.
Status Callback	`statusCallback`	`string`	The URL that will receive status updates for this message. Check the Webhooks section for details. Max length is 256 characters.
Status Callback Header	`statusCallbackHeader`	`string`	The custom Authorization header will be contained in the callback request. Max length is 256 characters.
Message ID	`messageId`	`string`	The ID of the message to react to. You can get it from the webhook trigger.
Reaction	`reaction`	`string`	Select a value from the drop down menu:`lovelikedislikelaughexlaimquestion-love-like-dislike-laugh-exlaim-question`

Action Authentication#

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

About LoopMessage#

iMessage API for two-way communication

More Ways to Connect LoopMessage + Zendesk#

Other Popular Integrations#

Send Reaction with LoopMessage API on New Ticket (Instant) from Zendesk API

Zendesk + LoopMessage

Send Reaction with LoopMessage API on Ticket Solved (Instant) from Zendesk API

Pipedream makes it easy to connect APIs for LoopMessage, Zendesk and 2,400+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,400+apps by most popular

1
-
24
of
2,400+
apps by most popular