loading...
No Results
  • Get Started
    • Welcome to GoInsight.AI
    • Quick Start
  • Knowledge 101
    • Key Concepts
    • Knowledge Base
    • LLM Selection Guide
    • Tool
    • Service
    • Data Security
  • Quick Chatbot
    • Build a Quick Bot
  • InsightFlow
    • InsightFlow Introduction
    • Types of InsightFlow
    • Node
      • Start
      • LLM
      • Knowledge Base Retrieval
      • Answer
      • Document Writing
      • Document Reading
      • HTTP Request
      • IF/ELSE
      • Question Classifier
      • Branch Aggregator
      • Multi branch Selector
      • Iteration
      • Auto-Continue
      • Template
      • Code
      • JSON Variable Extractor
      • Variable Assigner
      • Variable Extractor
      • KnowledgeFocus LLM
      • Agent
      • End
    • Publishing
      • Publishing an Interactive Flow
      • Publishing a Service Flow
      • Create Your First Workflow
  • Control & Management
    • Access Control
Home > Documentation > InsightFlow > Publishing

Publishing a Service Flow

Congratulations on creating your first workflow! Now, let's explore how to publish a Service Flow and trigger it. Service Flows can be published as:

  • A Service
  • An API call

Publishing a Service Flow as a Service

  1. Step 1: Click "Save and Publish" in the upper right corner to see the "Publish" button. After publishing, the options below will be active, and you can view the timeline of published versions in "Previous Version."
  2. Save and Publish a Service Flow

  3. Step 2: To publish as a sevice, click "Publish as" and select "Service". This allows the Service Flow to be referenced in new workflows, enhancing functionality.
  4. Step 3: In the pop-up window, set a name and description. Choose to make it a public tool node or restrict access to specific team members.
  5. Set Service Flow description and access

Tips: To reference published tools in your workflow:

  • Right-click in the new workflow to select "Add Node."
  • You'll see existing nodes and a "Services" column with all published tools available for use.

Reference published tools

Publishing common workflows as Services and applying them flexibly in new workflows can break down barriers between workflows and avoid task duplication. When handling complex processes, different services tools can be combined like building blocks. This approach not only improves efficiency but also inspires team creativity.

Publishing a Service Flow as an API call

Another option is to publish the Service Flow as an API call for easy HTTP access, simplifying integration.

  1. Step 1: Click "Publish as".
  2. Step 2: In the pop-up window, select "API call" and click on "Create API endpoint".
  3. select Create API endpoint

  4. Step 3: Fill in the basic information for the API. The API protocol uses a long-term token by default, but you can adjust the token's validity period according to business needs, such as one week, two weeks, one month, two months, or long-term.
  5. Fill in the basic information for the API

Note: The generated API is displayed only once, so be sure to save it for future use. It is recommended not to share the API with others.

The generated API

The published API will appear in the API Call List, with each execution recorded in the "Call List."

The published API will appear in the API Call List

Triggering a Service Flow

We may encounter situations where we want the workflow to run a specific number of times at a certain time and then stop automatically. Goinsight can help you achieve this! Simply customize the trigger, and it will run automatically.

  1. Step 1: Click "Trigger" under "Save and Publish".
  2. Triggering a Service Workflow

  3. Step 2: Set the start time, execution interval, number of executions, and end time. The workflow will run automatically based on these settings.
  4. Run the workflow automatically

Updated on: Jun 25, 2025
Prev Publishing an Interactive Flow
Next Create Your First Workflow
On this page
  • Publishing a Service Flow as a Tool
  • Publishing a Service Flow as an API
  • Triggering a Service Flow
loading...
No Results