​
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.

​
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.

Fill in inputs

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

View schema and metadata

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

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.

​
What next?