Issue Credential with Dock Certs API on New Ticket Added to View (Instant) from Zendesk API

Pipedream makes it easy to connect APIs for Dock Certs, Zendesk and 2,000+ other apps remarkably fast.

Trigger workflow on

New Ticket Added to View (Instant) from the Zendesk API

Next, do this

Issue Credential with the Dock Certs API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

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

Select this integration
Configure the New Ticket Added to View (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
6. Select a View ID
Configure the Issue Credential action
1. Connect your Dock Certs account
2. Select a Issuer Profile
3. Optional- Configure Anchor
4. Optional- Configure Persist
5. Optional- Configure Password
6. Optional- Select a Template Design
7. Select a Type
8. Configure Credential Subject
9. Optional- Select a Registry
10. Optional- Configure Expiration Date
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 Ticket Added to View (Instant) on Zendesk

Description:Emit new event when a ticket is added to the specified view

Version:0.0.2

Key:zendesk-ticket-added-to-view

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,
  key: "zendesk-ticket-added-to-view",
  name: "New Ticket Added to View (Instant)",
  description: "Emit new event when a ticket is added to the specified view",
  version: "0.0.2",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    viewId: {
      propDefinition: [
        common.props.app,
        "viewId",
      ],
    },
  },
  methods: {
    ...common.methods,
    getWebhookName() {
      return "Ticket Added To View Webhook";
    },
    getTriggerTitle() {
      return "Ticket Added To View Trigger";
    },
    getTriggerConditions() {
      return {
        any: [
          {
            field: "update_type",
            value: "Change",
          },
          {
            field: "update_type",
            value: "Create",
          },
        ],
      };
    },
    async isRelevant(payload) {
      const { tickets } = await this.app.listTicketsInView({
        viewId: this.viewId,
      });
      const foundTicket = tickets.find(({ id }) => id == payload.ticketId);
      return foundTicket;
    },
  },
};

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
View ID	`viewId`	`string`	Select a value from the drop down menu.

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#

Issue Credential on Dock Certs

Description:Issue a new credential. [See the documentation](https://docs.api.dock.io/#credentials)

Version:0.0.1

Key:dock_certs-issue-credential

View on GitHub

Dock Certs Overview#

The Dock Certs API provides a means for issuing verifiable credentials and decentralized identities, which are essential for managing digital proofs of various qualifications, memberships, or certifications. Using Pipedream's integration capabilities, you can automate the process of creating, revoking, and verifying these credentials. With Pipedream's serverless architecture, you can set up triggers and actions that respond to events in real-time, orchestrate data flow between Dock Certs and other services, and manage credentials with minimal manual intervention.

Action Code#

import dockCerts from "../../dock_certs.app.mjs";
import { ConfigurationError } from "@pipedream/platform";

export default {
  key: "dock_certs-issue-credential",
  name: "Issue Credential",
  description: "Issue a new credential. [See the documentation](https://docs.api.dock.io/#credentials)",
  version: "0.0.1",
  type: "action",
  props: {
    dockCerts,
    issuerProfile: {
      propDefinition: [
        dockCerts,
        "profile",
      ],
    },
    anchor: {
      type: "boolean",
      label: "Anchor",
      description: "Whether to anchor the credential on the blockchain as soon as it is issued. Defaults to false.",
      default: false,
      optional: true,
    },
    persist: {
      type: "boolean",
      label: "Persist",
      description: "Whether to store an encrypted version of this credential with Dock Certs. Defaults to false, if true you must supply password.",
      default: false,
      optional: true,
    },
    password: {
      type: "string",
      label: "Password",
      description: "Password used to encrypt the credential if you choose to store it. The same password must be used to retrieve the credential contents. Dock does not store this password.",
      optional: true,
    },
    template: {
      propDefinition: [
        dockCerts,
        "templateDesign",
      ],
    },
    type: {
      propDefinition: [
        dockCerts,
        "credentialType",
      ],
    },
    subject: {
      type: "string",
      label: "Credential Subject",
      description: "A unique identifier of the recipient. Example: DID, Email Address, National ID Number, Employee ID, Student ID, etc.",
    },
    status: {
      propDefinition: [
        dockCerts,
        "registry",
      ],
      description: "Identifier of the credential's revocation registry",
      optional: true,
    },
    expirationDate: {
      type: "string",
      label: "Expiration Date",
      description: "The date and time in GMT that the credential expired is specified in RFC 3339 format. The default value of the expirationDate will be empty if the user does not provide it.",
      optional: true,
    },
  },
  async run({ $ }) {
    if (this.persist && !this.password) {
      throw new ConfigurationError("Password required if `persist` is `true`.");
    }

    const data = {
      anchor: this.anchor,
      persist: this.persist,
      password: this.password,
      template: this.template,
      credential: {
        type: [
          this.type,
        ],
        subject: {
          id: this.subject,
        },
        status: this.status,
        issuer: this.issuerProfile,
        expirationDate: this.expirationDate,
      },
    };

    const response = await this.dockCerts.issueCredential({
      data,
      $,
    });

    if (response) {
      $.export("$summary", `Successfully issued credential with ID ${response.id}.`);
    }

    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
Dock Certs	`dockCerts`	`app`	This component uses the Dock Certs app.
Issuer Profile	`issuerProfile`	`string`	Select a value from the drop down menu.
Anchor	`anchor`	`boolean`	Whether to anchor the credential on the blockchain as soon as it is issued. Defaults to false.
Persist	`persist`	`boolean`	Whether to store an encrypted version of this credential with Dock Certs. Defaults to false, if true you must supply password.
Password	`password`	`string`	Password used to encrypt the credential if you choose to store it. The same password must be used to retrieve the credential contents. Dock does not store this password.
Template Design	`template`	`string`	Select a value from the drop down menu.
Type	`type`	`string`	Select a value from the drop down menu.
Credential Subject	`subject`	`string`	A unique identifier of the recipient. Example: DID, Email Address, National ID Number, Employee ID, Student ID, etc.
Registry	`status`	`string`	Select a value from the drop down menu.
Expiration Date	`expirationDate`	`string`	The date and time in GMT that the credential expired is specified in RFC 3339 format. The default value of the expirationDate will be empty if the user does not provide it.

Issue Credential with Dock Certs API on New Ticket Added to View (Instant) from Zendesk API

Pipedream makes it easy to connect APIs for Dock Certs, Zendesk and 2,000+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,000+apps by most popular

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