Skip to content
Griptape Cloud logoGitHub logo

Connect Griptape Cloud to GitHub

Move data between Griptape Cloud and GitHub the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Griptape Cloud triggers
4
Griptape Cloud actions
5
GitHub triggers
14
GitHub actions
19

Automation ideas

What you can build with Griptape Cloud and GitHub

A few flows teams run between Griptape Cloud and GitHub. Use one as a starting point, or build your own from scratch.

  • Assistant Run Completes in Griptape Cloud creates Create Issue in GitHub

    Trigger when an assistant run is completed (succeeded, failed, or cancelled)

  • New Pull Request in GitHub creates Create Assistant Run in Griptape Cloud

    Triggers when there is activity on a pull request.

  • Assistant Run Completes in Griptape Cloud creates Get issue information in GitHub

    Trigger when an assistant run is completed (succeeded, failed, or cancelled)

  • New Pull Request in GitHub creates Create Structure Run in Griptape Cloud

    Triggers when there is activity on a pull request.

  • Assistant Run Completes in Griptape Cloud creates Create comment on a issue in GitHub

    Trigger when an assistant run is completed (succeeded, failed, or cancelled)

  • New Pull Request in GitHub creates Get Assistant Run in Griptape Cloud

    Triggers when there is activity on a pull request.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Griptape Cloud and acts in GitHub, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.