Docs
Powered by

work.studio documentation

work.studio is three products that share one account, one set of connections, and one idea: your work already lives in systems you've chosen, and software should join those up rather than ask you to move.

Start here

Coordinate the work you're doing now.

Projects that accumulate their own context — the conversation, the tickets, the specs, the decisions — so a week later you don't have to reassemble it.

At my.work.studio.

Get started

Automate the work you do repeatedly.

Build a pipeline once and run it on a schedule, a webhook, or an event. Connect your apps, add logic, deploy.

Get started

Offer integrations to your own customers.

Put a white-labelled catalog inside your product. Your customers connect their own accounts, and you don't build or maintain connectors.

Get started

Which one do I want?

You want to… Use
Ask questions about a project and keep its context in one place My Studio
Run a process every time something happens Flow
Have a document or plan written into your team's Drive My Studio
Move data between two systems on a schedule Flow
Offer integrations to your own customers, inside your product Embed

My Studio and Flow share your connections, so anything you connect in one works in the other. Embed is the one to reach for when you're a software company and the integrations are for your customers.

Reference

Connections
API
Concepts

Connect Jira, GitHub, Drive, SharePoint, Slack and more — once, with your own account.

Connections →

The REST API, authentication, and the endpoint reference.

API docs →

The vocabulary — what a connection, a workflow, a project and a run actually are.

Concepts →

Getting help