Skip to content
Snowflake logoCloudConvert logo

Connect Snowflake to CloudConvert

Move data between Snowflake and CloudConvert 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.

Snowflake triggers
5
Snowflake actions
14
CloudConvert triggers
3
CloudConvert actions
7

Automation ideas

What you can build with Snowflake and CloudConvert

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

  • New Row in Snowflake creates Convert File in CloudConvert

    Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.

  • New Job Event in CloudConvert creates Run Query in Snowflake

    Triggers when a new job has been created

  • New Row in Snowflake creates Capture Website in CloudConvert

    Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.

  • New Job Event in CloudConvert creates Run Multiple Queries in Snowflake

    Triggers when a new job has been created

  • New Row in Snowflake creates Merge Files to PDF in CloudConvert

    Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.

  • New Job Event in CloudConvert creates Insert Row in Snowflake

    Triggers when a new job has been created

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 Snowflake and acts in CloudConvert, 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.