All templates

Automated Rive Animation Developer Handoff

Each time a Rive state machine is marked ready for export, WebRun logs its states and target platform to an Airtable handoff tracker, then emails the dev lead the export details and file link so the animation moves into development the same day.

Deploy this workflow Browse all templates

Runs on WebRun · Strict Lockdown policy

Runs each time a state machine is marked ready WebRunorchestrates each step

Rive check state machines marked ready

Airtable log the animation handoff

Gmail email the dev lead

In short

How do I hand off finished Rive animations to my development team?

WebRun watches your Rive file for state machines marked ready for export. Each time one is flagged, it logs the animation's states and target platform to an Airtable handoff tracker, then emails the dev lead the export details and file link, so interactive animations move into development the same day design finishes them.

Every ready animation gets handed off without a manual message
Developers get the export details and platform in one email
Design and development stay in sync on animation status

Built for App development teams · motion designers · product design teams · game studios

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

WebRun signs in and gets to work

Opens rive.app/login in a real browser with your saved login - no setup, no API keys.
1
Rive - check state machines marked ready
- Open the file and check for state machines marked ready for export
- Note the animation's name, states, and target platform
Done when Every ready state machine is listed with its details.
2
Airtable - log the animation handoff

airtable.com

WebRun logs the animation handoff in Airtable.
- Add a row for the animation to the handoff tracker
- Include its states, target platform, and export format
- Mark it ready for integration
Done when Every ready animation is logged in the tracker.
3
Gmail - email the dev lead

gmail.com

WebRun emails the dev lead.
- Email the dev lead with the animation's export details
- Attach the Rive file link and the Airtable row
- Note which screen or feature it's for
Done when The dev lead has the animation details needed to integrate it.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run

rive.app/login

ScheduleRuns automatically on this cadence

Runs each time a state machine is marked ready

DeliveryHow each run's result reaches you

Handoff details · Gmail

OutputWhat each run produces - A logged handoff for every ready animation in Airtable, with export details emailed to the dev lead.

List

Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.

Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST

Typed input ALLOW

Shell command BLOCK

File uploads BLOCK

Runs in a contained environment More on policies

Good to know

Questions, answered

Does it export or integrate the animation itself?

No. WebRun only logs the handoff and shares the details. Exporting the runtime file and integrating it into the app stays with the developer.

How does it know a state machine is ready?

It reads the ready-for-export status or tag the designer sets on the state machine in Rive, so nothing gets handed off before a human marks it done.

Can it handle animations for multiple platforms?

Yes. Each animation is logged with its target platform, whether iOS, Android, or web, so the dev lead knows which runtime to expect.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.

Deploy this workflow Talk to us