Meta tags:
description=Developer documentation for products at Zendesk;

Headings (most frequently used words):

api, zis, on, this, page, event, introduction, integration, services, top, level, properties, input, object, referencing, an, in, jobspec, configs, connections, inbound, webhooks, links, registry, trigger, events, at, least, once, delivery, sequencing,

Text of the page (most frequently used words):
event (50), the (47), events (31), #object (24), zis (19), sequence (18), zendesk (14), ticket (12), for (12), input (12), custom (11), flow (10), type (9), integration (9), this (9), tag (8), name (8), properties (8), api (8), with (7), trigger (7), contains (7), see (6), user (6), and (6), jobspec (6), example (6), may (6), action (6), property (6), connections (6), activity (5), legacy (5), support (5), organization (5), multiple (5), order (5), position (5), same (5), subdomain (5), created (4), data (4), meta (4), can (4), least (4), once (4), inbound (4), json (4), account (4), integration_key (4), account_id (4), top (4), level (4), reference (4), services (4), status (3), developer (3), event_type (3), event_source (3), you (3), job (3), referencing (3), doesn (3), guarantee (3), first (3), integer (3), string (3), information (3), about (3), ticket_event (3), sequencing (3), delivery (3), received (3), native (3), 2021 (3), 12t08 (3), 37z (3), webhooks (3), introduction (3), slack (2), sunshine (2), referenced (2), out (2), from (2), ids (2), positions (2), occur (2), before (2), after (2), total (2), triggered (2), description (2), following (2), event_domain (2), single (2), both (2), all (2), are (2), designed (2), fire (2), respective (2), could (2), times (2), post (2), new (2), through (2), each (2), domain (2), has (2), types (2), associated (2), custom_object_event (2), content (2), changes (2), key (2), 323401287712 (2), includes (2), access (2), using (2), when (2), specific (2), specs (2), page (2), registry (2), links (2), oauth (2), configs (2), zendev_horizontal (2), system, terms, privacy, notice, 181, fremont, street, 17th, floor, san, francisco, california, 94105, blog, forum, join, our, community, associate, specify, example_integration, example_flow, flow_name, ticketcreated, example_job_spec, spec, fifo, processing, process, sequences, 22222, 11111, similarly, not, always, have, don, use, basis, business, logic, number, within, that, were, update, comment, changed, include, however, result, running, message, tickets, messages, case, defined, webhook, receiver, body, http, request, activity_event, organization_event, user_event, depends, wrapper, retrieved, bundle, 37201638591, form_id, updated_at, submitter_id, problem, created_at, 41ea202e1, 123, external_id, 361454622831, organization_id, web, channel, via, 1001, 32040676813, brand_id, requester_id, my_tag1, tags, urgent, priority, null, group_id, 313502247511, assignee_id, 646602214, ref, occurred_at, version, c20565cd20591b5e81e2206e91adfb2a, my_zendesk_subdomain, my_integration_key, 12345, also, these, paths, right, executes, passes, into, step, path, then, installed, onto, where, will, run, tells, listen, describes, supported, used, building, bundles, integrations, clients, bearer, token, basic, authentication, home, search, documentation, docs,

Text of the page (random words):
introduction zendesk developer docs zendev_horizontal zendev_horizontal documentation api reference search integration services trigger events home integration services integration services zis configs api configs connections api all connections api key connections basic authentication connections bearer token connections oauth clients oauth connections zis inbound webhooks api inbound webhooks zis links api links zis registry api zis registry api integrations bundles job specs trigger events introduction ticket events user events organization events custom object events legacy custom object events activity events on this page top level properties input object at least once delivery event sequencing referencing an event in a jobspec introduction on this page top level properties input object at least once delivery event sequencing referencing an event in a jobspec this reference information describes supported zendesk events used to trigger a zis flow when building an integration with zendesk integration services zis both native zendesk event types and custom events received through inbound webhooks can be referenced in a jobspec object job specs are then installed onto the zendesk account where the integration will run this tells zis to listen for the specific event type on the account when the right type of event is received zis executes the associated flow and passes a json object into the first step of the flow this json object includes data about the event s specific changes in the input property you can access this property in the zis flow using the input reference path the json object also includes the account_id subdomain and integration_key properties you can access these properties in the zis flow using the respective account_id subdomain and integration_key reference paths example account_id 12345 integration_key my_integration_key subdomain my_zendesk_subdomain input ticket_event meta sequence id c20565cd20591b5e81e2206e91adfb2a position 1 total 9 version 1 0 occurred_at 2021 08 12t08 46 37z ref 18 646602214 type ticket created ticket assignee_id 313502247511 group_id null priority urgent tags my_tag1 requester_id 323401287712 brand_id 32040676813 id 1001 status new via channel web organization_id 361454622831 external_id 41ea202e1 123 created_at 2021 08 12t08 46 37z type problem submitter_id 323401287712 updated_at 2021 08 12t08 46 37z form_id 37201638591 top level properties an event contains the following top level properties property data type description account_id integer zendesk account id integration_key string integration key retrieved from the zis bundle subdomain string account subdomain input object contains information about the event s changes input object the input object content depends on the event type it contains a json wrapper for the event s data zendesk domain event property content ticket event ticket_event ticket events user event user_event user events organization event organization_event organization events custom object event custom_object_event custom object events legacy custom object event custom_object_event legacy custom object events activity event activity_event activity events each domain has multiple native event types each native event type has an associated tag in zis to trigger a flow in the case of user defined events received through an inbound webhook receiver the input object contains the body of the http request at least once delivery zendesk events are designed to fire at least once for a respective action however a single action could fire the same event multiple times this could result in a zis flow running multiple times for the same action for example a zis integration designed to post a slack message for new tickets may post multiple messages for the same ticket created event event sequencing a single action can trigger a sequence of events for example an update to a ticket may trigger both the comment created and status changed events all events include an input event_domain meta sequence object this object contains information about the event s sequence for example a ticket event contains the object in the input ticket_event meta sequence property the input event_domain meta sequence object contains the following properties property data type description id string id of the action that triggered the event events with the same sequence id were triggered by the same action position integer order of the event within the sequence zendesk doesn t guarantee this order total integer number of events in the sequence zendesk doesn t guarantee the order of sequence ids or sequence positions for example an event with a sequence id of 22222 may occur before or after an event with a sequence id of 11111 similarly an event with a sequence position of 2 may occur before or after an event with a sequence position of 1 a ticket created event may not always have a sequence position of 1 don t use the order of sequence ids or sequence positions as the basis for an integration s business logic zis doesn t guarantee a first in first out fifo processing of events zis may process events from multiple sequences out of order referencing an event in a jobspec an event is referenced in a job spec to trigger a flow example jobspec type zis jobspec properties name example_job_spec event_source support event_type ticket ticketcreated flow_name zis example_integration flow example_flow to associate a zendesk event with a flow you specify the event_source and the event tag name for event_type zendesk event event_source event_type ticket event support event tag name see ticket events user event support event tag name see user events organization event support event tag name see organization events custom object event support event tag name see custom object events legacy custom object event sunshine event tag name see legacy custom object events activity event sunshine event tag name see activity events join our developer community forum blog slack zendesk 181 fremont street 17th floor san francisco california 94105 privacy notice zendesk developer terms system status