Set Custom Ticket Fields with Zendesk API on New Stories from Dev.to API

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

Trigger workflow on

New Stories from the Dev.to API

Next, do this

Set Custom Ticket Fields 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 Dev.to 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 New Stories trigger
1. Configure Timer
2. Connect your Dev.to account
Configure the Set Custom Ticket Fields action
1. Connect your Zendesk account
2. Select a Ticket ID
3. Configure Custom Fields
4. 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#

New Stories on Dev.to

Description:Emit new Dev.to story

Version:0.0.4

Key:dev_to-fresh-stories

View on GitHub

Dev.to Overview#

The Dev.to API enables programmatic interaction with Dev.to, a community for software developers to share articles and engage with content. Through the API, you can automate content creation, management, and analysis. Accessing user articles, managing comments, and triggering actions based on Dev.to events are just a few capabilities at your disposal. By leveraging these with Pipedream's serverless platform, you can craft powerful automations that respond in real-time to activities on Dev.to, streamlining your content strategy and community engagement.

Trigger Code#

import devTo from "../../dev_to.app.mjs"; import moment from "moment"; import common from "../common.mjs"; export default { name: "New Stories", type: "source", key: "dev_to-fresh-stories", description: "Emit new Dev.to story", version: "0.0.4", props: { ...common.props, devTo, }, dedupe: "greatest", async run({ $ }) { const data = await this.devTo.getArticles($, { params: { per_page: 1000, top: 1, }, }); data.forEach((event) => { this.$emit(event, { id: event.id, ts: moment(event.published_timestamp).valueOf(), summary: event.title, }); }); }, };

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
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Timer	`timer`	`$.interface.timer`	How often to poll Dev.to for new articles
Dev.to	`devTo`	`app`	This component uses the Dev.to app.

Trigger Authentication#

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

About Dev.to#

Where programmers share ideas and help each other grow.

Action#

Set Custom Ticket Fields on Zendesk

Description:Sets one or more custom field values on a ticket. [See the documentation](https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/#update-ticket).

Version:0.0.2

Key:zendesk-set-custom-ticket-fields

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"; import { parseObject } from "../../common/utils.mjs"; import { ConfigurationError } from "@pipedream/platform"; export default { key: "zendesk-set-custom-ticket-fields", name: "Set Custom Ticket Fields", description: "Sets one or more custom field values on a ticket. [See the documentation](https://developer.zendesk.com/api-reference/ticketing/tickets/tickets/#update-ticket).", type: "action", version: "0.0.2", annotations: { destructiveHint: false, openWorldHint: true, readOnlyHint: false, }, props: { app, ticketId: { propDefinition: [ app, "ticketId", ], }, customFields: { type: "string[]", label: "Custom Fields", description: "Array of custom field objects. Each item should be formatted as `{\"id\": \"field_id\", \"value\": \"field_value\"}`. Example: `{\"id\": \"23129751115165\", \"value\": \"ABCDE\"}`", }, customSubdomain: { propDefinition: [ app, "customSubdomain", ], }, }, methods: { updateTicket({ ticketId, ...args } = {}) { return this.app.update({ path: `/tickets/${ticketId}`, ...args, }); }, }, async run({ $: step }) { const { ticketId, customFields, customSubdomain, } = this; // Parse custom fields from string array to objects const parsedCustomFields = parseObject(customFields); if (!Array.isArray(parsedCustomFields)) { throw new ConfigurationError("Custom Fields must be an array of custom field objects"); } // Validate custom fields structure parsedCustomFields.forEach((field, index) => { if (!field.id) { throw new ConfigurationError(`Custom field at index ${index} is missing required "id" property`); } if (field.value === undefined) { throw new ConfigurationError(`Custom field at index ${index} is missing required "value" property`); } }); const response = await this.updateTicket({ step, ticketId, customSubdomain, data: { ticket: { custom_fields: parsedCustomFields, }, }, }); step.export("$summary", `Successfully updated ${parsedCustomFields.length} custom field(s) on ticket ${response.ticket.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
Zendesk	`app`	`app`	This component uses the Zendesk app.
Ticket ID	`ticketId`	`string`	Select a value from the drop down menu.
Custom Fields	`customFields`	`string[]`	Array of custom field objects. Each item should be formatted as `{"id": "field_id", "value": "field_value"}`. Example: `{"id": "23129751115165", "value": "ABCDE"}`
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

Set Custom Ticket Fields with Zendesk API on New Stories from Dev.to API

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

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

Developers ♥ Pipedream

1-24of2,800+apps by most popular

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