OBJECT
ApplicationEntity
link GraphQL Schema definition
- type ApplicationEntity {
- # Tells if the entity instance is protected against delete (Entities that need to
- # be present in the system at any time). Delete action still may fail if entity is
- # deletable, due some other additional validations.
- : Boolean!
- # Unique identifier of entity.
- : ID!
- # Specifies if the entity is considered deleted.
- : Boolean
- # Last modification time.
- : DateTime
- # Creation time.
- : DateTime
- # Identifier of the matching Automation Hub item, or empty for user-defined
- # applications. Set automatically by Coevera when the application is registered
- # through the Automation Hub.
- : Int
- # True when this application can register webhooks. Set when the application is
- # created and cannot be changed afterwards.
- : Boolean!
- # True when this application is shown in the Automation Hub UI. Hidden
- # applications are still functional but excluded from end-user discovery.
- : Boolean!
- # Name of the entity and its default text representation.
- : String!
- # True when this application can act on behalf of individual users (personal
- # triggers). Set when the application is created and cannot be changed afterwards.
- : Boolean
- # Revision when entity was lastly changed.
- : Int
- # Per-context flags describing when this application is offered to users
- # (triggers, personal triggers, display, filter). Computed by Coevera.
- : ApplicationUseOption!
- # Is application active.
- : Boolean!
- # Checks which permissions current user has on concrete entity instance.
- #
- # Arguments
- # permissions: [Not documented]
- (: [EntityPermsEnum!]!): [EntityPermsEnum!]!
- }
link Require by
- ApplicationEntityEdgeA Relay edge containing a `ApplicationEntity` and its cursor.
- ApplicationRepositorynull
- ApprovalEntitynull
- CloudObjectEntitynull
- CloudObjectTemplateEntitynull
- EmailSequenceActivityLogEntitynull
- EmailSequenceEnrolledEntitynull
- ProcessActivityLogEntitynull
- ProcessScheduledActionEntitynull
- WebhookEntityRegistered webhook urls will be called when subscribed events occur with access level corresponding to the Webhook owner. Recipient has to receive the webhook in 10 seconds and respond with HTTP 200 (2XX) status. On failed delivery it will be retried up to 10 times within 24 hours. If the receiving side will respond with HTTP 410 status, the webhook will be disabled. Webhook is also disabled when we receive HTTP timeout on 10th retry and there was no successful delivery in last 5 days.