Go live

Until now, your batches read HubSpot but every built-in source answered from fixtures. Going live means real provider calls, which cost money, on real companies, which your team will be asked about. Do it on a short list first.

Before you switch

• npx motions check and npx motions test pass.
• Settings → CRM shows HubSpot, Read only and Token set, and the Lists tile shows your lists.
• Settings → Source keys shows Platform key or Tenant key for every provider your motions call. See Provider keys and secrets.
• Settings → Secrets has no Missing secrets.
• Every handle in approvers and every queue owner belongs to a member. See Your team and their handles.
• Each motion has a cap, so a mistake can’t spend more than you expect.

Rehearse, then open

1. Turn fixture mode off. In tenant.yaml, set sources: { fixtures: false }, or remove the line, and push. From now on, built-in sources call their providers and spend.

2. Make a short list in HubSpot. Five to ten companies you know well, including one or two that should trip each question.

3. Open a batch on it. In the app, Batches → Open batch: choose the motion, leave the version on the live one, pick the list, and give it a label like “rehearsal”. Or from the terminal:

   npx motions open v360 weekly --list "Rehearsal" --label rehearsal

4. Watch it run. Open the batch. Look for failed or parked companies: a failed cell shows the error, and the troubleshooting guide says what each one means. Check Sources for what the calls cost.

5. Answer and approve. The question owners answer from Questions or Today. When the changeset seals, check each proposed change against what you know about those companies.

6. Open the real batch. When the rehearsal looks right, open the motion on its real list.

Approved changes don't reach HubSpot yet

With HubSpot connected read-only, an approved changeset records each write as skipped. The changeset still shows every proposed change with its before and after, so for now someone applies the approved ones in HubSpot by hand.

The first week

• Today is everyone’s starting page: the questions that need them, the changesets waiting for their approval, and what’s running.
• Deadlines count in the tenant’s time zone. A question nobody answers by its deadline takes its queue’s default, so the batch never waits forever.
• Fixes are new versions. If a step is wrong, fix it in the repository, merge, and Upgrade the open batch: steps that changed run again, and companies already sealed in a changeset keep what was sealed. See Fix a stuck batch.