MotionHub

Add an existing account user to a project with a specific role. Requires admin permission on the project.

project_assign_user

Attach an existing project file to a card

board_card_attach_file

Attach a task to a card

board_card_attach_task

Link a task to a calendar event

calendar_event_attach_task

Get the cost-report summary for a budget version: budget vs committed (POs) vs actual vs EFC (Earned Final Cost) vs variance, broken down by schedule/account. Defaults to the budget's default version when version_id is omitted. All money figures are fringe-loaded on the same basis: budget_amount includes fringe on-costs, and committed_amount / actual_to_date / efc include fringe computed on realised spend, so a fully delivered line closes at zero variance. All figures are also NET of VAT: an actual stores a gross `amount` plus a derived `net_amount`, and the report sums the net so it is comparable with the budget, which has no tax component. Use committed_amount_excl_fringe / actual_to_date_excl_fringe to reconcile against a PO total or the NET of an invoice — not its gross face value — and realised_fringe_amount for the on-cost portion. A scoped Budget Contributor/Reader sees their granted schedules only. Returns paginated results (default 100, max 500).

budget_cost_report

Get an actuals-only pivot of recorded spend by shoot day, location, or department. Useful for "how much did we spend on day 4" / "total catering by location" questions. Figures are actuals at face value and EXCLUDE fringe on-costs — this pivot aggregates by dimension rather than by budget line, so per-line fringe rules do not apply. budget_cost_report carries the fringe-loaded figures. Returns paginated results (default 100, max 500).

budget_cost_report_pivot

Move a purchase order through its state machine: pending_approval → approved, approved → issued, issued → closed, or any → cancelled. Approving requires Budget Admin and cannot be done by the PO's creator; issuing and closing require Budget Admin; submitting, withdrawing and cancelling require PO write access on a PO you created. Side effect: notifies the other people involved in the approval (the budget admins, or the PO's creator) with an in-app alert, and emails them unless they have turned that category off. When the account has a Xero organisation connected, a PO that becomes approved, issued or cancelled is queued for sync to Xero: pushed automatically if it was synced before, otherwise held for a Budget Admin to review.

budget_po_transition

Check if a contact has overlapping calendar events across all projects in a date range. Use this before assigning contacts to events or when changing event dates.

calendar_check_contact_conflicts

Check if a team member has overlapping calendar events across all projects in a date range. Use this before assigning users to events or when changing event dates.

calendar_check_user_conflicts

Convert an approved/issued/closed purchase order into actual spend rows. This is the canonical way to record that a PO has been paid: it mints budget_actual rows tagged with source=po_conversion and source_po_id=<this PO>, so the cost report offsets them against the PO's committed amount instead of double-counting. Idempotent — rerunning skips already-converted lines. This is the path for spend fulfilling a specific PO; budget_actual_create covers spend with no PO behind it. Side effect: when the account has a Xero organisation connected, each new actual is queued for sync to that Xero organisation, and the project's Budget Admins get an in-app alert and an email asking them to review the push.

budget_po_convert_to_actual

Create a new kanban board in a project

board_create

Create a new card in a board column

board_card_create

Add a new column to a board

board_column_create

Record a new actual (spend) against a budget line. Use this for spend that does NOT correspond to an existing PO (cards, payroll, ad-hoc invoices). For spend fulfilling an existing PO, budget_po_convert_to_actual is the corresponding tool: it tags the actual with source_po_id so the cost report offsets it against the PO's committed amount rather than double-counting. Defaults to posted status; pass status=draft to create as a draft for review. budget_line_id is required for posted actuals. VAT is computed server-side from vat_code_id: `amount` is the GROSS you pay the supplier, and net_amount / vat_amount are derived from it. Omit vat_code_id and the record defaults to NO_VAT (net = gross), which is what the cost report will then show — set a code when the invoice carried VAT. Side effect: when the account has a Xero organisation connected, a posted actual is queued for sync to that Xero organisation, and the project's Budget Admins get an in-app alert and an email asking them to review the push.

budget_actual_create

Create a new budget line under a schedule/account. Pass quantity, rate, and x_factor here whenever you know them — they seed every version cell in one round trip and the response echoes the seeded cells back under line_versions. Per-version variations, and later edits to those cells, belong to budget_line_version_update.

budget_line_create

Create a new schedule/category in the budget. Optionally nests under an existing account via parent_id.

budget_account_create

Create a custom tag definition for the budget. Tags are attached to lines via budget_line_tag_attach.

budget_tag_create

Create a new calendar event in a project

calendar_event_create

Create a new calendar group in a project

calendar_group_create

Create a new calendar row in a project

calendar_row_create

Create a new company/client

company_create

Create a new contact. Requires account admin permission.

contact_create

Create a fringe rule template (e.g. NI, pension, holiday pay). A rule is applied to a schedule by budget_fringe_attach_account, or to a single line by budget_fringe_attach_line.

budget_fringe_rule_create

Create a new programme. Requires account admin permission.

programme_create

Create a new project. Requires account admin permission. Auto-assigns users flagged with add_to_future_projects.

project_create

Create a new purchase order in draft state. PO number is auto-assigned per project; reference holds the supplier's own quote, contract or order reference, carried to Xero as the PO Reference if the PO is later approved and pushed (this tool itself does not contact Xero). Line items are added with budget_po_line_create, and budget_po_submit puts the PO forward for approval. Pass at least one of contact_id or company_id so the PO has a recipient.

budget_po_create

Add a new empty scene to a script

script_scene_create

Create a new script in a project. Types: "filming" (production script) or "edit" (editing script)

script_create

Create a new task in a project

task_create

Delete a board and all its columns, cards, and attachments

board_delete

Delete a card and all its attachments

board_card_delete

Delete a column. Must have no cards assigned and board must have at least 2 columns.

board_column_delete

Delete one or more calendar events

calendar_event_delete

Delete one or more calendar groups

calendar_group_delete

Delete one or more calendar rows

calendar_row_delete

Delete a comment and all its replies

board_card_delete_comment

Remove a link from a card

board_card_delete_link

Remove a scene from a script

script_scene_delete

Delete one or more scripts

script_delete

Delete one or more tasks

task_delete