Limitations

Everything the platform can’t do yet, in one list. Each page that runs into one of these says so where it matters.

Getting started

• Pruma creates tenants. There’s no sign-up. Ask Pruma for a tenant, and an invitation for its first owner.
• Invitations aren’t e-mailed. Creating one gives you a link: send it yourself. It’s good for a week.
• No self-serve password reset. An admin of your tenant makes you a link from Settings → Members, under Password reset link… in your row’s menu. It works once, within the hour.
• The command line and SDK aren’t on npm yet. @motionskit/cli and @motionskit/sdk haven’t had their first release. Ask Pruma for the packages.
• motions init is behind. It names an approver owner and writes a GitHub workflow you can’t use from a tenant repo. Start from the Quickstart’s files.

CRM

• HubSpot is read-only. Motions reads companies, contacts, deals, owners, notes and lists from HubSpot, but doesn’t write to it yet. Changesets still go through approval, and each change gets a skipped receipt. Only the test CRM is written to. See Connect HubSpot.
• HubSpot is the only real CRM.
• The HubSpot token can only be pasted once the tenant is on HubSpot. The token form appears in Settings → CRM after a push with system: hubspot in crm.yaml.
• Changing system in crm.yaml forgets the stored token. Pushing a different system, by mistake or on purpose, means an admin has to paste the token again.
• Batches start from a CRM list of companies, or company ids. There’s no spreadsheet upload, and contact or deal lists don’t work.

Building motions

• motions push doesn’t say why a motion was refused when the reason is one check can’t see. It prints invalid manifest. The usual cause is a misspelt operation in a step’s sources; see Error messages.
• motions check doesn’t check operation names against the catalog. push does.
• motions test only runs motion tests. Run a custom source’s tests with npx vitest run sources.
• Custom sources aren’t answered from fixtures in batches. Fixture mode covers built-in sources; custom sources call their real API. In tests, runStep answers both from fixtures.
• The Brazilian registry sources (cnpj.*) need the platform configured for them. If they fail with BULL_API_URL is not set, ask Pruma.

Running

• A tenant has one CRM. To rehearse on the test CRM while the tenant is on HubSpot, ask Pruma for a second tenant.
• The simulated clock can only be started through the API. See Testing.
• There’s no hosted GitHub action. Use the workflow in Publish from GitHub, which runs the command line.
• The app is https://motions.pruma.tech. Set MOTIONS_URL to that. These docs are https://docs.pruma.tech.