Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

GoogleCloudIntegrationsV1alphaTriggerConfig

import type { GoogleCloudIntegrationsV1alphaTriggerConfig } from "https://googleapis.deno.dev/v1/integrations:v1.ts";

Configuration detail of a trigger.

interface GoogleCloudIntegrationsV1alphaTriggerConfig {
description?: string;
errorCatcherId?: string;
label?: string;
nextTasksExecutionPolicy?: "NEXT_TASKS_EXECUTION_POLICY_UNSPECIFIED" | "RUN_ALL_MATCH" | "RUN_FIRST_MATCH";
properties?: {
[key: string]: string;
}
;
trigger?: string;
triggerId?: string;
triggerNumber?: string;
triggerType?:
| "TRIGGER_TYPE_UNSPECIFIED"
| "CRON"
| "API"
| "SFDC_CHANNEL"
| "CLOUD_PUBSUB_EXTERNAL"
| "SFDC_CDC_CHANNEL"
| "CLOUD_SCHEDULER"
| "INTEGRATION_CONNECTOR_TRIGGER"
| "PRIVATE_TRIGGER"
| "CLOUD_PUBSUB"
| "EVENTARC_TRIGGER";
}

§Properties

§

Optional. An alert threshold configuration for the [trigger + client + integration] tuple. If these values are not specified in the trigger config, default values will be populated by the system. Note that there must be exactly one alert threshold configured per [client + trigger + integration] when published.

§

Optional. Cloud Scheduler Trigger related metadata

§
description?: string
[src]

Optional. User-provided description intended to give additional business context about the task.

§
errorCatcherId?: string
[src]

Optional. Optional Error catcher id of the error catch flow which will be executed when execution error happens in the task

§

Optional. List of input variables for the api trigger.

§
label?: string
[src]

Optional. The user created label for a particular trigger.

§
nextTasksExecutionPolicy?: "NEXT_TASKS_EXECUTION_POLICY_UNSPECIFIED" | "RUN_ALL_MATCH" | "RUN_FIRST_MATCH"
[src]

Optional. Dictates how next tasks will be executed.

§

Optional. List of output variables for the api trigger.

§

Optional. Informs the front-end application where to draw this error catcher config on the UI.

§
properties?: {
[key: string]: string;
}
[src]

Optional. Configurable properties of the trigger, not to be confused with integration parameters. E.g. "name" is a property for API triggers and "subscription" is a property for Pub/sub triggers.

§

Optional. Set of tasks numbers from where the integration execution is started by this trigger. If this is empty, then integration is executed with default start tasks. In the list of start tasks, none of two tasks can have direct ancestor-descendant relationships (i.e. in a same integration execution graph).

§
trigger?: string
[src]

Optional. Name of the trigger. Example: "API Trigger", "Cloud Pub Sub Trigger" When set will be sent out to monitoring dashabord for tracking purpose.

§
triggerId?: string
[src]

Optional. Auto-generated trigger ID. The ID is based on the properties that you define in the trigger config. For example, for an API trigger, the trigger ID follows the format: api_trigger/TRIGGER_NAME Where trigger config has properties with value {"Trigger name": TRIGGER_NAME}

§
triggerNumber?: string
[src]

Required. A number to uniquely identify each trigger config within the integration on UI.

§
triggerType?: "TRIGGER_TYPE_UNSPECIFIED" | "CRON" | "API" | "SFDC_CHANNEL" | "CLOUD_PUBSUB_EXTERNAL" | "SFDC_CDC_CHANNEL" | "CLOUD_SCHEDULER" | "INTEGRATION_CONNECTOR_TRIGGER" | "PRIVATE_TRIGGER" | "CLOUD_PUBSUB" | "EVENTARC_TRIGGER"
[src]

Optional. Type of trigger