Updated Ticket

This card monitors for tickets that are updated within Zendesk.

Note: It takes up to 15 minutes for new or updated records in Zendesk to hit the Zendesk API, meaning the designer can't read new or updated records for at least 15 minutes after the time they are created. This means that the Run Now feature won't work for testing Flows that start with a Zendesk monitor. Please wait 20 minutes after creating or updating records for the monitor to run naturally in order to test Zendesk monitors in your Flows.

Output Fields

Any custom fields that exist will appear under 'Record'.

  • Record

    • id (text): The ID of the ticket.

    • url (text): The URL of the ticket.

    • external_id (text): An ID that you can assign to match this ticket with your own records.

    • type (text): The type of ticket.  Can be "problem", "incident", "question" or "task".

    • subject (text): The subject of the ticket.

    • description (text): The first comment on a ticket.

    • priority (text): The priority of the ticket. Can be "urgent", "high", "normal", or "low".

    • status (text): The state of the ticket.  Can be "new", "open", "pending", "hold", "solved", or "closed".

    • recipient (text): The email address of the original recipient of the ticket.

    • requested_id (text): The ID of the user who requested the ticket.

    • submitter_id (text): The ID of the user who submitted the ticket.  The submitter will is the author of the first comment on the ticket.

    • assignee_id (text): The ID of the agent to whom the ticket is assigned.

    • collaborator_ids (text): A comma-delimited list of the IDs of the users who are currently CC'd on the ticket.

    • organization_id (text): The ID of the organization of that the requester belongs to.

    • group_id (text): The ID of the group the user is assigned to.

    • forum_topic_id (text): The ID of the forum topic that the ticket originated from, if any.

    • problem_id (text): The ID of the problem that the ticket (if incident) is linked to, if any.

    • has_incidents (text): Returns 'true' if the ticket type is 'problem'.  Returns 'false' otherwise.

    • due_at (text): The due date of the ticket if it is of type 'task'.

    • tags (text): A comma-delimited list of the tags associated with the ticket.

    • via (text): A description of how the ticket was created (for example, "api", "web", "mobile").

    • satisfaction_rating (text):  The satisfaction rating of the ticket, or the state of satisfaction ("offered" or "unoffered").

    • sharing_agreement_ids (List): A list of numbers of the sharing agreement IDs used for this ticket.

    • followup_ids (List): A list of numbers of the follow up ticket IDs used for this ticket.

    • ticket_form_id (text): The ID of the brand associated with this ticket.

    • brand_id (text): The ID of the brand associated with this ticket.

    • public? (True/False): True or false about whether the ticket is publicly viewed or not.

    • created_at (text): Date and time that the ticket was created (for example, 2016-05-24T13:41:22Z).

    • updated_at (text): Date and time that the ticket was most recently updated.

See also