helmut.cloud
  • Introduction
    • Introduction
    • The key features of helmut.cloud
    • 🔥Case study: A media postproduction
  • Getting Started
    • Step 1: Sign up
    • Step 2: Create an organization
    • Step 3: Create a workflow
    • Step 4: Install the helmut.cloud Agent
    • Step 5: Run your first workflow
  • The helmut.cloud Agent
    • Install the helmut.cloud Agent software
      • MacOS
      • Windows
      • Docker
    • Establish a connection with the helmut.cloud Agent
      • MacOS and Windows
      • Docker (Linux)
    • helmut.cloud Agent logs
      • Windows and MacOS
      • Docker
    • Update the helmut.cloud Agent
  • Personal Account
    • Account settings
      • My profile
      • Security
      • Notifications
      • License (private organization)
      • Logs (private org)
      • Delete my account
  • Organizations
    • What are organizations in helmut.cloud?
    • View my organizations
      • Being a target
    • Choosing an organization to work in
    • Organization settings
      • Licenses for shared organizations
      • License
      • Logs (organization)
  • Members and teams
    • Members and roles
    • Invite members and assign roles
    • What is a team in helmut.cloud?
    • Create a team and add members
  • High5
    • What is High5?
    • Spaces in High5
      • List, create, rename and delete spaces
      • Events
      • Space dashboard
      • Agents
      • Webhooks
      • Secrets Store
      • User Access
      • Space settings
    • Organization dashboard
    • Stream Designer Studio
      • UI overview
      • Node inputs and outputs
    • Developing nodes with NodeKit
  • Changelog
    • 🎉Changelog
Powered by GitBook
On this page
  • Back to Stream Designer Studio
  • Aaaand - action!
  • Troubleshooting and logs
  1. Getting Started

Step 5: Run your first workflow

PreviousStep 4: Install the helmut.cloud AgentNextInstall the helmut.cloud Agent software

Last updated 1 year ago

Back to Stream Designer Studio

Now that your agent is installed and configured, it can be used to execute streams. Change back into the Stream Designer Studio and have a look to the upper right corner. Next to the little cloud symbol, is a tag that informs you if your agent is connected or not. Because we did that just a few moments ago, chances are that it still shows as disconnected.

Click on the symbol and choose your agent from the list below. Click "Connect". The connection will be established.

To test your stream before you use the webhook to trigger it, you can first save, then publish and finally test it with the buttons in the stream control tool bar on the middle upper edge of the canvas. There is a payload stated when testing. Right now, we do not use it, so you can simply ignore it.

If something goes wrong, you can check the debuggers log for errors to resolve the problem.

Aaaand - action!

The moment has come, tension rises: You can now use the webhook and trigger it with CURL from a terminal.

  • Open a terminal (and check if you have CURL installed)

  • Copy the webhooks URL from the your spaces webhooks-section by clicking the little pasteboard icon next to the name

  • Enter this prompt into your terminal and replace the placeholder with your webhook-URL:

curl "https://app.helmut.cloud/api/high5/v1/org/MyOrganization/placeholder" \
-H "knockknock:itsme" -H "content-type:application/json" -d "{}"

If your hello-world website opens in your browser now: Congratulations, you made it! 🥳

Troubleshooting and logs

You can later observe if your webhook accepted the trigger by clicking on the name in the webhooks-section and view the logs. If you get a 204, this is fine, because we did not send any content in the payload of the call. Click on the entry to view some details about the call, like headers and payload or response.

Your dashboard tells you wether your stream succeeded or failed. You can successfully trigger a webhook, but have a failing stream when something went sideways.

The helmut.cloud agent connection button in SDS lets you connect an agent with matching context
The stream control toolbar: save - publish - reload - debugger - exchange - snapshot - test
Make a click your webhook to view the details of the call, like header, body and return
A look into your spaces dashboard gives you an wider overview of all streams executed