INPUT_OBJECT

CreateEventActionTemplate

link GraphQL Schema definition

1input CreateEventActionTemplate {
4
2# The name of template. e.g. "Run engine X for every new mention in a watchlist".
3name: String!
8
5# Application this template could be applied to. If application_id is null, then
6# this is an org-wide template.
7ownerApplicationId: ID
12
9# use "event" for now. In the future, we allow additional input_type types. For
10# example, a schedule or a tweet.
11inputType: EventActionTemplateInputType!
17
13# based on the input_type, input_validation describes additional validations. For
14# example, if input_type is "event", input_validation could be a list of allowed
15# events.
16inputValidation: JSONData
22
18# A JSON structure that is compatible/specific to the input_type. For example, if
19# input type is "event", then input_attributes simply contain the entire event
20# payload.
21inputAttributes: JSONData
26
23# Either "job", "webhook", "sms", "email". Future action_type could be "gql"
24# where action is purely a function call.
25actionType: EventActionTemplateActionType!
31
27# Allows you to specify validation for the action_type. For example, if
28# action_type is "job", perhaps only whitelist a list of engines that could be
29# called.
30actionValidation: JSONData
35
32# dedicated column to specify where/what the action is taking place. For example,
33# if action is a job, then destination is an engine_id. For webhook, a uri.
34actionDestination: String!
41
36# A JSON structure that is compatible with action_type. For example, if
37# action_type is "webhook", action_attributes contain the mustache compatible
38# template to format the content. If action_type is "job", then action_attributes
39# need to specify a job template.
40actionAttributes: JSONData
42}