Skip to main content

​
What you’ll learn

By the end of this tutorial, you’ll learn how to:
  • Call REST APIs via the core.http_request action
  • Trigger workflows manually via the UI
  • Add secrets to your workflows

​
Prerequisites

​
Your first workflow

Tracecat uses YAML to define inputs and configurations for actions and workflows. YAML is a human-readable configuration language that is easy to write and read. It is also more concise than JSON and more customizable than HTML forms.If you’re new to YAML or need a refresher, check out our YAML syntax cheatsheet. YAML is also widely used in DevOps tools like Ansible, GitHub Actions, and Docker Compose.
Click the Create new button in the top right corner of the workflows page.Create workflow
Click on the empty workflow canvas to open the workflow settings panel. You can change the name and description of the workflow here.Rename workflow
To add a new node to the workflow, either drag out the actions dropdown menu from the trigger node or right click on the workflow canvas.View available actions
Search for and select the core.http_request action.Add HTTP action
Click on the core.http_request node and fill in the inputs. Tracecat uses YAML to define action inputs. Press the cmd+s or ctrl+s keys to save your inputs.
url: https://api.open-meteo.com/v1/forecast
method: GET
params:
  latitude: 37.773972
  longitude: -122.431297
  current: temperature_2m,precipitation_probability
Fill in HTTP request inputs
Before you can run your workflow, you need to save it. You must explicitly save your workflow for changes to take effect in workflow runs.Save workflow
Click the Run button to execute your workflow.You can ignore the sample webhook payload. In a future tutorial, we will learn how to pass custom payloads into workflows manually via UI or webhook.Run workflow
You can view the status of your most recent run in the left side panel. Select actions row by row to view their inputs and outputs.
  • Events
  • Action input
  • Action result
View events
You can view the required and optional inputs for an action under the Input schema section.View input schema

​
Actions and integrations

Actions are the building blocks of Tracecat workflows. Tracecat has two main types of actions:
  • core actions for core functionality (e.g. HTTP request, AI action, and data transforms).
  • tools actions for integrations to 3rd-party services.
Find out more in Tracecat’s core actions and tools docs.
Tracecat uses JSONPath and dot notation to select outputs from previous actions. JSONPath can also be used to filter and transform nested JSONs.Both ACTIONS and TRIGGER expression contexts support JSONPath syntax. If you are new to JSONPath or need a refresher, check out our JSONPath syntax cheatsheet.

Search for integrations

Search for pre-built integrations in the actions dropdown menu. Do this by right clicking on the workflow canvas or dragging it out from an existing node.View available actions

Fill in inputs

Fill in the required and optional inputs in the Inputs section.Action inputs

View schema and metadata

Expand the Input schema section to view all supported inputs and required secrets.Action input schema

View template

Click on the View template tab to view the YAML code for Action Template integrations. You can also view the integration’s action type, origin, and documentation URL at the top of the action’s settings panel.View template

​
What next?

⌘I