Motions docs

Motions runs a recurring go-to-market routine, such as “every week, check these 200 accounts, find the right people and get them ready in HubSpot”, as code that lives in git. Each run covers a list of companies, asks people the questions that need a person, and writes to the CRM only after someone approves.

These docs describe what the platform does today. Where something isn’t built yet, the page says so, and Limitations lists all of it in one place.

Start where you are

You’re setting Motions up for your company or for a client. Read What is Motions, run the Quickstart on the built-in test CRM, then follow Set up a tenant to connect HubSpot and bring your team in.

You write the motions. Start with How a motion is built, then go through the guides in order. The reference covers every field and function.

You answer questions or approve CRM writes. Read Run a batch and Answer and approve. You don’t need the command line.

What is MotionsBatches, steps, questions and changesets, in plain words.

QuickstartFrom an empty folder to a written CRM note.

Set up a tenantThe checklist for a new tenant owner.

GlossaryEvery term, with the Portuguese one you may already use.

Using Claude Code or another AI assistant

The docs are written so an assistant can follow them too. Point it at a page, or at Write motions with Claude Code, which gives it the rules a motion has to follow and the commands that check its work.

Words in code

Commands and file names appear as they’re typed: motions push, motion.yaml. Placeholders are in angle brackets, like <tenant>; replace them, brackets included.