{"id":21774,"date":"2023-08-29T05:08:00","date_gmt":"2023-08-29T05:08:00","guid":{"rendered":"https:\/\/help.kanidesk.com\/en\/docs\/automations\/configuring-workflow-rules\/sending-ticket-data-to-third-party-tools-using-trigger-webhook-option\/"},"modified":"2026-03-17T20:43:58","modified_gmt":"2026-03-17T20:43:58","slug":"sending-ticket-data-to-third-party-tools-using-trigger-webhook-option","status":"publish","type":"docs","link":"https:\/\/help.desk365.io\/en\/articles\/sending-ticket-data-to-third-party-tools-using-trigger-webhook-option\/","title":{"rendered":"Sending ticket data to third-party tools using ‘Trigger Webhook’ option"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t
\n Available with:<\/span>\n \n \n \n <\/circle>\n <\/path>\n <\/svg>\n Standard<\/span>\n <\/span>\n \n |<\/span>\n \n \n \n <\/circle>\n <\/path>\n <\/svg>\n Plus<\/span>\n <\/span>\n \n |<\/span>\n \n \n \n <\/circle>\n <\/path>\n <\/svg>\n Premium<\/span>\n <\/span>\n<\/div>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

In today’s fast-paced digital world, businesses have a whole array of tools and software at their disposal to make their operations run smoother. One important part of this whole process is sending ticket data to third-party tools using the trigger webhook option.<\/p>

Trigger Webhooks can be incredibly useful in Desk365 as part of an automation workflow. By creating this workflow rule, Desk365<\/a><\/span> can send data from the newly created ticket to an external application via a webhook.<\/p>

This can enable businesses to integrate Desk365 with other tools or systems they use, such as CRMs, marketing automation platforms, or project management tools.<\/p>

For example, businesses can use webhooks to pass only L3 support tickets to a different third-party solution, automatically create a new lead or contact in their CRM when a new ticket is created, or to trigger a specific action in a project management tool such as creating new tasks in Asana, and more.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\"desk365-trigger-webhooks-in-automations-setting-condition\"\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

In addition, the webhook option allows businesses to choose between making a POST or GET call when sending data to an external application.<\/p>

They can also make use of basic and advanced webhook options to pass ticket properties and other relevant data to the receiving application.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\"trigger-webhooks-in-desk365-automations-rule\"\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

By leveraging webhooks in automation rules, businesses can create highly customized and streamlined workflows that seamlessly integrate Desk365 with their existing systems and tools.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"author":6,"featured_media":0,"parent":18821,"menu_order":7,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-21774","docs","type-docs","status-publish","hentry","no-post-thumbnail"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/21774","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/comments?post=21774"}],"version-history":[{"count":37,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/21774\/revisions"}],"predecessor-version":[{"id":36090,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/21774\/revisions\/36090"}],"up":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/18821"}],"next":[{"title":"Auto assign to agent who responds to ticket using ticket updates","link":"https:\/\/help.desk365.io\/en\/articles\/auto-assign-to-agent-who-responds-to-ticket-during-ticket-updation\/","href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/18827"}],"prev":[{"title":"Automation using groups","link":"https:\/\/help.desk365.io\/en\/articles\/automation-using-groups\/","href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/18829"}],"wp:attachment":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/media?parent=21774"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/doc_tag?post=21774"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}