WarpBuild LogoWarpBuild Docs

Quickstart

Create your first Helios workflow in 5 minutes, automate everything.

Quickstart

This guide walks you through creating your first project, setting up integrations, and building your first workflow.

Create Project

Projects organize related workflows, variables, and integrations.

  1. Navigate to Projects in sidebar
  2. Click Create Project
  3. Fill in details:
    • Name: Descriptive project name
    • Description: Optional purpose description
  4. Set Visibility:
    • Organization: All team members can access
    • Restricted: Only explicitly granted users
  5. Click Create

Your project now contains workflows, variables, secrets, integrations, and team access settings.

Set Up Integrations

Integrations connect workflows to external services securely.

  1. Go to your project → Integrations
  2. Select a service
  3. Choose authentication method:
    • Helios App: Built-in OAuth (recommended)
    • API Key: Enter service API key
    • BYO App: Use your OAuth credentials
  4. Name your integration for easy identification

For detailed setup instructions and examples, see the Integrations section.

Create Your First Workflow

Let's build a workflow that posts GitHub issues to Slack.

  1. In your project, click Create Workflow
  2. Name: "GitHub Issue to Slack"
  3. Description (optional): "Post new GitHub issues to Slack channel"

Trigger

Triggers are the starting point of a workflow. They can be configured to listen to events from external services, or periodically run on a schedule.

The payload of the trigger is available in the {{ trigger.payload }} variable. You can use it in any node.

Example

Listen for new issues in a GitHub repository. Select the Integration Trigger node and select the GitHub integration you created in the previous step.

Prompt it in natural language to listen for new issues in the ExampleOrg/ExampleRepo repository as follows:

Listen for new issues in the `ExampleOrg/ExampleRepo` repository of the type `bug`.

The prompt is used to filter the events that are delivered to the workflow. No additional processing is done on the input payload. Use nodes to process the input payload as needed for your workflow. For example, the following is an invalid filter prompt:

Listen for new issues in the `ExampleOrg/ExampleRepo` repository of the type `bug` and identify if the issue is a duplicate of an existing issue.

The following is a valid filter prompt:

Listen for new issues in the `ExampleOrg/ExampleRepo` repository of the type `bug`.

Add Integration

Select the Slack node and select the Slack integration you created in the previous step.

Prompt it in natural language to post a message to the #dev-alerts channel as follows:

Post a message to the #dev-alerts slack channel with the details of the issue. Format it as a markdown message with the title, author, and link to the issue.
Include the issue priority and category.

Issue details are here:
`{{ trigger.payload }}`.

The input and output of each node is available in the {{ nodes['node-name'].input }} and {{ nodes['node-name'].output }} variables.

Run the Workflow

Create a new issue in the ExampleOrg/ExampleRepo repository to see the workflow run. You can:

  • See the workflow run in the Workflow Runs tab.
  • See the logs of the workflow run in the Logs tab.
  • Change the workflow and re-run it by redelivering the trigger payload.

Next Steps

Explore advanced features:

  1. User roles and permissions - Manage team access
  2. Sharing options - Share projects and integrations
  3. Manage Variables and Secrets - Manage variables and secrets
  4. Workflow YAML definition - Advanced workflow customization
  5. Keyboard shortcuts - Boost productivity
  6. Available integrations - Connect more services
  7. Key concepts - Deepen your understanding

Support

Email [email protected] for assistance or reach out through the in-app chat.

Last updated on