Changelog

Video deliverables: short clips from your data

A deliverable can now be a video. Ask a specialist for a 15-second ad, a product launch clip, or a monthly recap, and it writes the animation and renders it into a video you play right in the deliverable, with play, seek, and full screen. A recap can read your connected accounts, such as Stripe or Google Sheets, so this month's figures are the ones on screen. It plays on the web and in the mobile app, its card shows the poster with a play mark, and it is shared like any other deliverable.

How it works

  • Rendered when it changes, never when it's opened. Publishing a video renders it, and so does a refresh that brings new data. Opening it plays the last render.
  • One render at a time per workspace. A render takes about twice the video's length; the next one waits its turn while the last finished video keeps playing.
  • Up to a minute, up to 1920 pixels a side. Landscape, portrait, and square, at 24 to 60 frames a second. A render uses credits for its sandbox time, like a refresh.
  • When a render fails, its specialist sees why. The deliverable says it couldn't render, the specialist reads exactly what went wrong, and Refresh tries again once it's fixed.
  • Download the MP4. One button in the viewer saves the video.

Also shipped

  • A deliverable that is one fixed-size frame, such as a story graphic, now opens whole and centred on screen, on the web and on your phone.
  • Download a deliverable from the side panel it opens in from a chat, in every format it exports.
  • Refresh says when a deliverable has nothing to refresh, and why.

Your first specialist starts here.

Give it one job. Build the workflows, apps, and skills to get it done.