---
title: "Trigger"
slug: "dataflow-trigger-vpc"
tags: ["Data Flow"]
updated: 2026-10-08T07:02:58Z
published: 2026-10-08T07:02:58Z
canonical: "guide.ncloud-docs.com/dataflow-trigger-vpc"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Trigger

Available in VPC

This guide describes the **Trigger** interface layout and how to create triggers. A trigger is a file that specifies a task schedule. Trigger cannot operate alone and operates when integrated with a job during workflow configuration. To add a trigger as a workflow configuration component, see [Create workflow](/docs/en/dataflow-workflow-vpc#%EC%9B%8C%ED%81%AC%ED%8F%B4%EB%A1%9C%EC%83%9D%EC%84%B1).

## Trigger interface

The trigger interface includes the following components: ![Screen shot September 14, 2026 2.19.58 PM.png](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/%E1%84%89%E1%85%B3%E1%84%8F%E1%85%B3%E1%84%85%E1%85%B5%E1%86%AB%E1%84%89%E1%85%A3%E1%86%BA%202026-09-14%20%E1%84%8B%E1%85%A9%E1%84%92%E1%85%AE%202.19.58.png?sv=2026-02-06&spr=https&st=2026-11-14T04%3A40%3A33Z&se=2026-11-14T05%3A40%3A33Z&sr=c&sp=r&sig=QAY9taZoJDuN3VVZCBG5ngE2SKMvGEJ0vK%2Bin2NhNdU%3D)

| Component | Description |
| --- | --- |
| ① Menu name | Current menu name. |
| ② Basic features | Features displayed when you first access the **Trigger** menu. - **[Create triggers]**: Click to [create a job](/docs/en/dataflow-trigger-vpc#%ED%8A%B8%EB%A6%AC%EA%B1%B0%EC%83%9D%EC%84%B1). - **[Learn more about the product]**: Go to the Data Flow overview page. - **[Refresh]**: Reload the current page. |
| ③ Post-creation features | Features available after creating a trigger - **[Delete]**: [Delete a trigger](/docs/en/dataflow-trigger-vpc#%ED%8A%B8%EB%A6%AC%EA%B1%B0%EC%82%AD%EC%A0%9C) that is selected. |
| ④ Trigger list | List of triggers created. [View settings information](/docs/en/dataflow-trigger-vpc#%ED%8A%B8%EB%A6%AC%EA%B1%B0%EC%A0%95%EB%B3%B4%ED%99%95%EC%9D%B8) for each trigger. |

## View trigger information

To view the settings information on a created trigger:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Big Data & Analytics** > **Data Flow**.
2. Click the **Trigger** menu.
3. When the trigger list appears, view the trigger information.
  - **Trigger name**: The unique name entered by the user when creating a trigger
  - **Run option**: The run option entered by the user when creating a trigger. One of the following values is displayed: Recurring execution, Cloud Functions event, or Manual execution.
  - **Execution cycle**: The execution cycle set by the user when creating a trigger. Example: Every Tuesday, daily 15:00.
  - **Update date and time**: Created date and time of the trigger
  - Click a trigger to expand its details below the list, where you can view the execution type, execution method or event source, creation date and time, and the associated workflow. For triggers with the **Event** execution type, the [execution guide](/docs/en/dataflow-trigger-vpc#CloudFunctions%EC%9D%B4%EB%B2%A4%ED%8A%B8%ED%8A%B8%EB%A6%AC%EA%B1%B0%EC%84%A4%EC%A0%95) is also displayed.

## Create triggers

To create a trigger:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Big Data & Analytics** > **Data Flow**.
2. Click the **Trigger** menu.
3. Click **[Create Trigger]**.
4. In the Create trigger popup, enter the following items:
  - **Name**: Enter the trigger name. Use 3 to 100 characters consisting only of uppercase and lowercase letters, numbers, hyphens (-), and underscores (*). The value must begin with a letter or an underscore (*).
  - **Execution type**: Select one of the following options: Schedule, Event, or Manual execution.
    - **Schedule**: Automatically run the workflow at a specified cycle or at a specific date and time.
    - **Event**: A Cloud Functions Action that receives an external event calls the DataFlow execution API to run the workflow.
    - **Manual execution**: Not executed automatically. Used when a user runs a workflow directly from the console.
  - Execution method: If **Schedule** is selected as the **execution type**: Select either Recurring execution or One-time execution
  - When selecting **Recurring execution** as the execution, **Execute cycle**: Select hourly, daily, weekly, or monthly.
  - When selecting Execution cycle **Weekly**, **Execution week**: Select the week for the workflow to run. Multiple selections allowed.
  - When selecting Execution cycle **Monthly**, **Execution date**: Enter the date between 1 to 31. Separate multiple dates with commas (,). If **Last day of month** is selected, the workflow also runs on the last day of each month. In this case, you do not need to enter a date.
  - When selecting **Recurring execution** as the execution method, **Run time**: Enter the time for the workflow to run.
    - When selecting **Hourly** as the execution cycle: Enter a number between 0 and 59 to specify the minute at which the workflow runs each hour. Example: 30 (Run at 30 minutes past every hour)
    - When selecting **Daily**, **Weekly**, or **Monthly** as the execution cycle: Enter the execution time in HH:mm format. Example: 12:00
  - When selecting **One-time execution** as the execution method, **execution date**: Click the ![i-dataflow_calendar](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/i-dataflow_calendar.png?sv=2026-02-06&spr=https&st=2026-11-14T04%3A40%3A33Z&se=2026-11-14T05%3A40%3A33Z&sr=c&sp=r&sig=QAY9taZoJDuN3VVZCBG5ngE2SKMvGEJ0vK%2Bin2NhNdU%3D) icon, select the date and time to run the workflow, and then click **[Apply]**. The execution date and time must be at least 5 minutes later than the current time.
  - When selecting **Event** for the execution type, **Event source**: Select Cloud Functions. No additional input fields are required. After creating the trigger, you must configure a Cloud Functions Action to call the Data Flow execution API for the workflow to run. For more information about the configuration procedure, refer to [Configuring Cloud Functions event triggers](/docs/en/dataflow-trigger-vpc#CloudFunctions%EC%9D%B4%EB%B2%A4%ED%8A%B8%ED%8A%B8%EB%A6%AC%EA%B1%B0%EC%84%A4%EC%A0%95).
  - When selecting **Manual execution** for the execution type: No additional input field is required
5. Click **[Create]**.
  - Creating a trigger is complete and is shown on the trigger list.
  - The created trigger is registered on NAVER Cloud Platform as resource. For more information, see [Resource Manager concepts](/docs/en/management-rmgr-1-1-2).

## Delete triggers

To delete a trigger:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Big Data & Analytics** > **Data Flow**.
2. Click the **Trigger** menu.
3. Select the specific trigger from the trigger list, and click **[Delete]**.
  - The trigger is deleted from the trigger list.
  - Workflows that include a deleted trigger no longer run.

## Set a Cloud Functions event trigger

Triggers with the **Event** execution type run the associated workflow when a Cloud Functions Action calls the Data Flow workflow execution API. You can use triggers supported by Cloud Functions, such as Object Storage file uploads, Cron schedules, and API Gateway requests, as workflow execution conditions.

For the configuration sequence, follow these steps:

1. [Create](/docs/en/dataflow-trigger-vpc#%ED%8A%B8%EB%A6%AC%EA%B1%B0%EC%83%9D%EC%84%B1) a trigger with the **Event** execution type and add it to the workflow that you want to run. To add a trigger to the workflow, see [Create workflow](/docs/en/dataflow-workflow-vpc#%EC%9B%8C%ED%81%AC%ED%8F%B4%EB%A1%9C%EC%83%9D%EC%84%B1).
2. In the **Trigger** menu, click the trigger in the trigger list to expand its details. Check the following items:
  - **Associated workflow**: Copy the workflow ID
  - **Execution guide**: Click **[View Sample Code]** to copy the Python sample code for use in a Cloud Functions Action
3. In the Cloud Functions console, create an Action by using the copied sample code. Then, register `NCLOUD_ACCESS_KEY`, `NCLOUD_SECRET_KEY`, and `DATAFLOW_WORKFLOW_ID` as default parameters, and connect a Cloud Functions trigger that will be used as the workflow execution condition to the Action.
  - For detailed procedures on creating an Action, connecting a trigger, and verifying execution results, refer to [Cloud Functions sample code - Data Flow integration](https://github.com/NaverCloudPlatform/cloud-functions/tree/master/samples/python/dataflow/workflow).