Creating a New Workflow

You can create a new workflow to automatically connect file, email, search, AI, and notification tasks.


Creating a New Workflow

  1. In the left menu, select My Workflows or Team Workflows.
  2. Select + New Workflow.
  3. Enter a Workflow Name.
  4. Enter a Description if needed.
  5. Select Create.

Creating a new workflow

Setting Up a Trigger

A trigger is the condition that starts a workflow. You can set it to run manually, run at a set time, or run when an event occurs, such as a file or mail event.

  1. On the editing screen, select the Trigger block.
  2. Check the Trigger Type in the settings panel on the right.
  3. Select the trigger type to use.
  4. Enter the values required for that trigger type.
  5. Use Test Trigger to verify the condition.

Trigger settings panel

Trigger Types

The trigger types currently available are as follows.

TriggerTypical Use
Manual ExecutionThe user runs the workflow directly, whenever needed.
ScheduleRuns the workflow at a set time or recurring interval.
WebhookRuns the workflow when an external system sends a request.
File Creation DetectedRuns when a new file is created in the specified location.
Modification DetectedRuns when the specified file or location is modified.
Email ReceivedRuns when an email matching the conditions arrives.

When using a file-related trigger, you can also configure a Watch Path and a File Pattern (GLOB).

Adding Blocks

A block is an action that runs after the trigger. It can read a file, summarize with AI, save a result, or notify a user.

  1. Select the + button below the trigger.
  2. Use Search Blocks or the categories to find the block you need.
  3. Select the block.
  4. Enter the required values in the settings panel on the right.
  5. Use Test Step to verify the block behaves as expected.

Workflow add-block button

Block selection window

Frequently Used Blocks

You can add many different kinds of blocks to a workflow. The blocks available may continue to grow over time.

CategoryBlockTypical Use
External requests & collectionHTTP RequestCall an external URL or API.
External requests & collectionURL CollectionFetch a web page's content for use in the next step.
AIAI PromptSummarize or classify files, emails, or search results.
FileRead FileRead the contents of an existing file and pass it to the next step.
FileWrite FileSave the workflow's result as a new file.
FileList FilesList the files at a specific location.
SearchNaver SearchFetch Naver search results.
SearchWiki SearchFetch wiki-based search results.
SearchKIPRIS SearchFetch KIPRIS search results such as patents and trademarks.
MailSend MailSend an email to the specified recipients.
MailInboxFetch the list of emails in the inbox.
NotificationSend NotificationSend a popup-style notification within SetFN.
NotificationSend DMSend a DM to a specific user.
Code & logicRun CodeExecute JavaScript code.
Code & logicConditional BranchSplit the execution flow based on a condition.
Code & logicWaitWait a specified amount of time before the next step.

Good use cases

  • When you want a file upload to trigger an AI summary and have the result saved as a file
  • When you want to check the content of an incoming email and notify the person in charge
  • When you want to collect a specific URL or search results to draft a report

Example: Notify the Person in Charge After Receiving an Email

You can send a notification so the person in charge sees it right away when a client email or inquiry email arrives.

  1. Set the trigger to Email Received.
  2. Use an AI Prompt block to summarize the email content.
  3. Use a Conditional Branch block to determine whether the email is important.
  4. If it's important, run a Send Notification or Send DM block.
  5. Save the summary to a file if needed.

Saving and Activating

  1. Once configuration is done, select Save.
  2. Test any step marked Test Required first.
  3. If there are no issues, select Activate.
  4. On the list screen, confirm that the workflow's activation toggle is turned on.

Good to Know

  • If You have unsaved changes is displayed, there are unsaved changes remaining.
  • File writes, sending mail, and sending DMs can affect real data or users, so activate only after testing.
  • Team workflows can affect team users.
  • Block names and availability may change with updates.