Delete Ticket with Zendesk API on Response Created from Formbricks API

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

Trigger workflow on

Response Created from the Formbricks API

Next, do this

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

Select this integration
Configure the Response Created trigger
1. Connect your Formbricks account
2. Select one or more Survey IDs
Configure the Delete Ticket action
1. Connect your Zendesk account
2. Select a Ticket ID
3. Optional- Configure Custom Subdomain
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#

Response Created on Formbricks

Description:Emit new event when a response is created for a survey. [See the documentation](https://formbricks.com/docs/api/management/webhooks)

Version:0.0.1

Key:formbricks-response-created

View on GitHub

Formbricks Overview#

Formbricks is a flexible tool for building forms that can integrate seamlessly into any website. The API allows for rich interactions with the forms you create, enabling you to automate the gathering and processing of data. By plugging the Formbricks API into Pipedream, you can harness serverless workflows to react to form submissions in real-time, store responses, or trigger a multitude of actions across different platforms. Think of it as empowering your forms to communicate and act on the data without manual intervention.

Trigger Code#

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

export default {
  key: "formbricks-response-created",
  name: "Response Created",
  description:
    "Emit new event when a response is created for a survey. [See the documentation](https://formbricks.com/docs/api/management/webhooks)",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    formbricks,
    http: "$.interface.http",
    db: "$.service.db",
    surveyIds: {
      propDefinition: [
        formbricks,
        "surveyIds",
      ],
    },
  },
  methods: {
    getTriggers() {
      return [
        "responseCreated",
      ];
    },
    _getWebhookId() {
      return this.db.get("webhookId");
    },
    _setWebhookId(value) {
      this.db.set("webhookId", value);
    },
  },
  hooks: {
    async activate() {
      const data = {
        surveyIds: this.surveyIds,
        triggers: this.getTriggers(),
        url: this.http.endpoint,
      };

      const { id } = await this.formbricks.createWebhook({
        data,
      });
      this._setWebhookId(id);
    },
    async deactivate() {
      const id = this._getWebhookId();
      if (id) {
        await this.formbricks.deleteWebhook({
          id,
        });
      }
    },
  },
  async run({ body }) {
    const { data } = body;
    if (data) {
      this.$emit(body, {
        id: data.id,
        summary: `New response by ${
          data.personAttributes?.email ??
          data.person?.attributes?.email ??
          "(unknown user)"
        }`,
        ts: Date.parse(data.createdAt),
      });
    }
  },
};

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
Formbricks	`formbricks`	`app`	This component uses the Formbricks app.
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.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Survey IDs	`surveyIds`	`string[]`	Select a value from the drop down menu.

Trigger Authentication#

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

About Formbricks#

Open-source Experience Management. Understand what customers think & feel about your product. Natively integrate user research with minimal dev attention, privacy-first.

Action#

Delete Ticket on Zendesk

Description:Deletes a ticket. [See the documentation](https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/#delete-ticket).

Version:0.1.2

Key:zendesk-delete-ticket

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.

Action Code#

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

export default {
  key: "zendesk-delete-ticket",
  name: "Delete Ticket",
  description: "Deletes a ticket. [See the documentation](https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/#delete-ticket).",
  type: "action",
  version: "0.1.2",
  props: {
    app,
    ticketId: {
      propDefinition: [
        app,
        "ticketId",
      ],
    },
    customSubdomain: {
      propDefinition: [
        app,
        "customSubdomain",
      ],
    },
  },
  methods: {
    deleteTicket({
      ticketId, ...args
    } = {}) {
      return this.app.delete({
        path: `/tickets/${ticketId}`,
        ...args,
      });
    },
  },
  async run({ $: step }) {
    const {
      ticketId,
      customSubdomain,
    } = this;

    await this.deleteTicket({
      step,
      ticketId,
      customSubdomain,
    });

    step.export("$summary", "Successfully deleted ticket");

    return true;
  },
};

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
Zendesk	`app`	`app`	This component uses the Zendesk app.
Ticket ID	`ticketId`	`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`

Action 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