Recent searches


No recent searches

Zach Anthony's Avatar

Zach Anthony

Joined Oct 16, 2021

·

Last activity Feb 18, 2025

Zendesk Product Manager

Following

0

Followers

0

Total activity

109

Votes

0

Subscriptions

50

ACTIVITY OVERVIEW

Latest activity by Zach Anthony

Zach Anthony commented,

Community comment Developer - Zendesk Apps Framework (ZAF)

Hi Jorge Pinon , thanks for flagging this issue. It looks like we missed updating this documentation previously, so I've gone ahead and organized to have this updated.

View comment · Posted Feb 18, 2025 · Zach Anthony

0

Followers

0

Votes

0

Comments


Zach Anthony created an article,

ArticleDeveloper updates
Announced on Rollout starts Rollout ends
October 28, 2024 December 5, 2024 December 5, 2024

We’re announcing an upcoming update to the way that OAuth connections can be referenced within Zendesk Integration Services (ZIS) flows and custom actions.

This announcement includes the following topics:

What is changing?

Historically, developers using ZIS could reference the access token of an OAuth connection in a flow or custom action using the path $.connections.{oauth_connection_name}.access_token.

When Zendesk announced support for additional authentication methods in ZIS connections, we introduced a new way to make use of connections in ZIS actions with the connectionName property.

Until now, both referencing methods were supported. Going forward, bundles can no longer be uploaded or updated if they contain an OAuth access token reference path.

Why is Zendesk making this change?

This change will keep your credentials safer and further limits the opportunities for them to be exposed or captured by an attacker.

What do I need to do?

No immediate action is required, as flows currently running will continue to execute without issue. However, developers who are either creating a new bundle or updating an existing ZIS bundle must make sure to eliminate any references to an OAuth access token reference path. Instead, use the connectionName property to refer to the connection in your custom action definitions. For more information, refer to Using a connection to authenticate API requests in a ZIS flow.

If you have feedback or questions related to this announcement, visit our community forum where we collect and manage customer product feedback. For general assistance with your Zendesk products, contact Zendesk Customer Support.

Edited Oct 25, 2024 · Zach Anthony

0

Followers

1

Vote

0

Comments


Zach Anthony commented,

Community comment Developer - Zendesk Apps Framework (ZAF)

Hi Sebastian, you're absolutely correct that secure settings cannot be transformed prior to the request being made out to the destination server.  I can appreciate that for authentication schemes which require computation at run time, such as with HMAC, it is problematic. I've gone ahead and captured your feedback and we will consider how we might be able to address this limitation in future.
 

To securely cater for this use case today, you would need to ensure that the request is made server side; this would involve some middleware between your app that is able to support an alternative authentication scheme.

 

View comment · Posted Oct 14, 2024 · Zach Anthony

0

Followers

0

Votes

0

Comments


Zach Anthony commented,

Community comment Developer - Zendesk Apps Framework (ZAF)

Hi Nate Koterba , thanks for flagging this issue. As of version 1.0.0-beta.47, the login command no longer requires '/token' to be appended to your email address. Ill be sure to make sure this is updated in our documentation accordingly.

View comment · Posted Aug 26, 2024 · Zach Anthony

0

Followers

0

Votes

0

Comments


Zach Anthony created an article,

ArticleDeveloper updates
Announced on Rollout starts
August 2, 2024 August 2, 2024

We're excited to announce the release of a new feature that allows customers to initiate automated workflows in response to changes in custom object records, offering more ways to keep their data synchronized across systems.

This announcement includes the following topics:

What is changing?

Developers using Zendesk Integration Services (ZIS) can now trigger flows when custom object records are created, updated, or deleted. Previously, this was only possible for legacy custom object records.

Why is Zendesk making this change?

By adding support for these additional trigger events, we're continuing to make it easier for customers to take advantage of custom objects to deliver great customer experiences. This update allows customers to monitor changes to custom object records and trigger workflows in their business systems.

What do I need to do?

The new custom object record trigger events are available now. For more information, see ZIS Trigger Events in our developer documentation.

If you have feedback or questions related to this announcement, visit our community forum where we collect and manage customer product feedback. For general assistance with your Zendesk products, contact Zendesk Customer Support.

Edited Aug 02, 2024 · Zach Anthony

0

Followers

1

Vote

0

Comments


Zach Anthony created an article,

ArticleDeveloper updates
Announced on Rollout starts Rollout ends
April 9, 2024 April 9, 2024 April 9, 2024

 

Zendesk is thrilled to announce two key improvements that make it easier for you to create integrations using Zendesk Integration Services (ZIS).

The first enhancement is a set of resource management API endpoints for ZIS. These new endpoints allow you to list and delete key resources such as bundles, integrations, and jobspecs. This makes it easier to build integrations with ZIS, maintain them while they are in use, and remove them when they are no longer required.

At the same time, we’re creating a stronger association between ZIS bundles and the resources they contain, simplifying the process of maintaining your integrations.

This announcement includes the following topics:

What is changing?

We have added several new endpoints to the ZIS APIs:

  • List Integrations
  • List Bundles
  • Show Bundle
  • Delete Bundle
  • List JobSpecs

We’ve also made bundles a more specific and permanent resource. Now, bundles will be persistent resources that you can create, fetch, update, and delete. We’ve also tightened up bundle validation logic to avoid the same action, flow, or jobspec being defined in multiple bundles.  Moving forward, a given resource can only be defined in one bundle.

Why is Zendesk making this change?

We have heard feedback that it can be hard to keep track of ZIS resources throughout the development lifecycle. Until now, it has been difficult for customer developers to answer questions such as:

  • Which integrations exist in my account?
  • What business logic is contained in an integration's flows?
  • Are the integration's flows active or inactive?
  • Why did a bundle's behavior change when I modified an action or jobspec in another bundle?
  • How can I tidy up my Zendesk instance by removing resources I no longer need?

These new features empower customers to retrieve information about the ZIS resources on their own account, enabling them to make updates or deletions with confidence.

What do I need to do?

These new features are available now. Learn more in the ZIS API reference.

If you have feedback or questions related to this announcement, visit our community forum where we collect and manage customer product feedback. For general assistance with your Zendesk products, contact Zendesk Customer Support.

Edited Apr 10, 2024 · Zach Anthony

3

Followers

5

Votes

2

Comments


Zach Anthony commented,

Community comment Developer - Zendesk APIs

Hi rahul siddu, unfortunately we don't support this event type today. Thanks for sharing this use case though. I've looped in Carl Joseph who is the PM looking after webhooks, to see if this is something that is currently planned on our roadmap.

View comment · Posted Jan 30, 2024 · Zach Anthony

0

Followers

0

Votes

0

Comments


Zach Anthony commented,

Community comment Developer - Zendesk Apps Framework (ZAF)

Hi Ali,

You are correct regarding the part required to listen to webhooks. You can find the full list of available event types here. Ticket events are currently only available via a linked trigger, so for your use case you will need to subscribe to `conditional_ticket_events`. You will then need to set up a trigger that references the webhook (which can also be done via apps requirements). You can refer to our Creating and monitoring webhooks guide for more general information about how webhooks can be used with Support triggers and this section around creating dependent apps requirements.

 

 

View comment · Posted Nov 14, 2023 · Zach Anthony

0

Followers

0

Votes

0

Comments


Zach Anthony commented,

Community comment Developer - Zendesk Apps Framework (ZAF)

It turns out that we did in fact release support for this today, hope this helps with everyone's use cases.

View comment · Posted Nov 14, 2023 · Zach Anthony

0

Followers

0

Votes

0

Comments


Zach Anthony commented,

Community comment Developer - Zendesk Apps Framework (ZAF)

Hi Ali,

You can use apps requirements to declare webhooks as requirements. With apps requirements, when an admin installs the app, Zendesk will create the app's required resources in the admin's account automatically.

You can take a look at this guide in our developer docs for more information on how to do this for webhooks.

Hope this helps!

View comment · Posted Nov 13, 2023 · Zach Anthony

0

Followers

1

Vote

0

Comments