Start Automation Flow with Triggre API on Ticket Pending (Instant) from Zendesk API

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

Trigger workflow on

Ticket Pending (Instant) from the Zendesk API

Next, do this

Start Automation Flow with the Triggre 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 Triggre action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the Ticket Pending (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 Start Automation Flow action
1. Connect your Triggre account
2. Configure Flow Name
3. Configure Flow Data
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 Pending (Instant) on Zendesk

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

Version:0.2.2

Key:zendesk-ticket-pended

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 Pending (Instant)",
  key: "zendesk-ticket-pended",
  type: "source",
  description: "Emit new event when a ticket has changed to pending status",
  version: "0.2.2",
  dedupe: "unique",
  methods: {
    ...common.methods,
    getWebhookName() {
      return "Ticket Pending Webhook";
    },
    getTriggerTitle() {
      return "Ticket Pending Trigger";
    },
    getTriggerConditions() {
      return {
        all: [
          {
            field: "update_type",
            value: "Change",
          },
          {
            field: "status",
            operator: "value",
            value: "pending",
          },
        ],
      };
    },
  },
};

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#

Start Automation Flow on Triggre

Description:Starts an automation flow within your Triggre application. [See the documentation](https://docs.triggre.com/lessons/how-to-create-an-incoming-web-api)

Version:0.0.1

Key:triggre-start-automation-flow

View on GitHub

Triggre Overview#

The Triggre API offers a gateway to interact with the Triggre platform, enabling you to automate processes, manage data, and integrate with other services. On Pipedream, you can harness this API to create powerful serverless workflows, connecting Triggre with numerous other apps to streamline operations, trigger actions based on events, and manipulate data in real-time. This empowers you to build custom, automated solutions that bridge the gap between Triggre and the rest of your tech stack.

Action Code#

import triggre from "../../triggre.app.mjs";

export default {
  key: "triggre-start-automation-flow",
  name: "Start Automation Flow",
  description: "Starts an automation flow within your Triggre application. [See the documentation](https://docs.triggre.com/lessons/how-to-create-an-incoming-web-api)",
  version: "0.0.1",
  type: "action",
  props: {
    triggre,
    flowName: {
      propDefinition: [
        triggre,
        "flowName",
      ],
    },
    flowData: {
      propDefinition: [
        triggre,
        "flowData",
      ],
    },
  },
  async run({ $ }) {
    const response = await this.triggre.startAutomationFlow({
      $,
      flowName: encodeURI(this.flowName),
      flowNameWithUnderscores: this.flowName.replace(/ /g, "_"),
      data: this.flowData,
    });
    $.export("$summary", `Successfully started automation flow ${this.flowName}`);
    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
Triggre	`triggre`	`app`	This component uses the Triggre app.
Flow Name	`flowName`	`string`	The name of the automation flow to start
Flow Data	`flowData`	`object`	The data to pass to the automation flow

Action Authentication#

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

To retrieve your Application Environment, Username and Password,

Navigate to https://my.triggre.com and sign in
Click on one of your applications on the left
Some buttons will appear, from those, click on "Application settings"
Your are taken to your application's connection page, click on "View connection credentials" at the bottom.
Copy your application's environment, username and password from the table on the right.