Skip to content
Griptape Cloud logoSupabase logo

Connect Griptape Cloud to Supabase

Move data between Griptape Cloud and Supabase 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
Supabase triggers
1
Supabase actions
9

Automation ideas

What you can build with Griptape Cloud and Supabase

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

  • Assistant Run Completes in Griptape Cloud creates Upload File in Supabase

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

  • New Row in Supabase creates Create Assistant Run in Griptape Cloud

    Fires when a new row is created in a table

  • Assistant Run Completes in Griptape Cloud creates Create Row in Supabase

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

  • New Row in Supabase creates Create Structure Run in Griptape Cloud

    Fires when a new row is created in a table

  • Assistant Run Completes in Griptape Cloud creates Update Row in Supabase

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

  • New Row in Supabase creates Get Assistant Run in Griptape Cloud

    Fires when a new row is created in a table

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 Supabase, 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.