最近搜索


没有最近搜索

Emily Prachnau's Avatar

Emily Prachnau

已加入2021年10月16日

·

最后活动2021年10月16日

关注

0

关注者

0

活动总数

5

投票

0

订阅

2

活动概览

的最新活动 Emily Prachnau

Emily Prachnau 创建了一个帖子,

帖子 Feedback - Sales CRM (Sell)

Feature Request Summary: 

Zendesk Sell deals firehose API endpoint should have every field that the Core API deals endpoint has. Right now, the firehose API doesn't not have every field that the core API has. For example, the firehose API is missing the unqualified_reason_id for deals.

Description/Use Cases: 

An application continuously consumes from the deals firehose API endpoint (/v3/deals/stream) and actions are triggered on certain changes. One of these actions requires the unqualified reason. Since the unqualified_reason_id is missing, the app has to do an additional lookup at the deals endpoint (v2/deals) to get the unqualified_reason_id field. 

With this workaround, the application doesn't know what the unqualified_reason was before it was changed.

Business impact of limitation or missing feature:

We aren't able to track the unqualified_reasons using the deals firehose API, which is valuable for gathering data and monitoring why deals were unqualified.

已于 2021年8月20日 发布 · Emily Prachnau

1

关注者

1

投票

0

评论


Emily Prachnau 进行了评论,

社区评论 Q&A - Sales CRM (Sell)

Thanks Kaja, I'll post it there.

查看评论 · 已于 2021年8月20日 发布 · Emily Prachnau

0

关注者

0

投票

0

评论


Emily Prachnau 创建了一个帖子,

帖子 Q&A - Sales CRM (Sell)

I have an application that consumes from the firehose API /v3/deals/stream endpoint and the unqualified_reason_id field is not present.

If I query /v2/deals, then the unqualified_reason_id field is present.

Are there plans to add unqualified_reason_id to the firehose API for deals so that it matches v2 endpoint?

已于 2021年8月18日 发布 · Emily Prachnau

0

关注者

2

投票

2

评论