SIGNALS Docs
Reader View

Workflow Record Steps

Create and update business records with workflow steps, delegated permissions and retry protection.

Create rental (rentals.create)

Records → Create rental adds a rental for a fixed account or the account that started the workflow. Account child events already resolve to their owning account. Supply a name (which supports {{ }} workflow variables), Start and End as +N days at HH:MM, Enquiry or Quote, an optional warehouse and notes. Times are relative to the captured trigger time; omitting the warehouse uses the existing accessible warehouse default. Accounts do not currently have a default-warehouse field.

The step needs rentals.create and accounts.view; Quote also needs rentals.edit. It returns rental as a workflow.rental.reference, including its id and number. Test run previews the account and dates. Repeating an attempt reuses its effect receipt.

Create account (accounts.create)

Records → Create account adds a Company, Contact or Venue. Supply a name (with optional workflow variables), type, optional email, phone and notes. Parent account uses the existing contact-to-company/venue relationship rules; there is no separate account hierarchy.

The step needs accounts.create and the applicable account field permissions, including accounts.identity.edit. Contact details require accounts.contact-pii.edit; duplicate-email checking also requires account, identity and contact-detail read access. An existing email causes the step to fail with the existing account number. Parent relationships require accounts.edit and accounts.view.

The output is account, a workflow.account.reference containing id and number. Test run previews the name; retries reuse the receipt. Both create steps can run without a live trigger record, and the normal record-created events retain the originating workflow chain.

Update record (records.update)

Records → Update record changes selected details through the record’s own update rules. Choose the record type, then the record that started the workflow, a matching record from a preceding step, or Find by ID. An ID may be literal or inserted from the trigger or a preceding step. The trigger option requires a matching subject type; account child events use their owning account.

Type Available details Permissions
Rental Name, Reference, Description, Customer notes, Priority rentals.view, rentals.edit
Account Name, Description, External reference, Rating, Job title, Department accounts.view, accounts.edit, accounts.identity.edit
Catalogue item Name, Description, SKU, Barcode, Weight, Active, Discountable, Can be added on its own, External reference catalogue-items.view, catalogue-items.edit
Asset Serial number, Barcode, Location, External reference assets.view, assets.adjust
Vehicle Name, Registration, Description, Active, Payload, Volume, Width, Height, Length vehicles.view, vehicles.edit

Eligible scalar custom fields are also available. Role-restricted, inactive, computed, automatic and multi-value fields are unavailable; restrictions are checked again when the workflow runs. Other record types show why they are unavailable. Warehouse moves, reassignment, rental dates and status, stock quantities, costs, credit, contact details and foreign keys need their own actions. For rental status use Change rental status.

The author must have the type’s edit permission to publish. The workflow service principal needs the view, edit and field permissions listed above, and the record must be within its warehouse scope. User accounts and deleted records cannot be targets.

Text, number, decimal and date fields accept Insert value expressions from the frozen run context. Yes/no and choice values use fixed selections. Names and titles retain special characters such as &. An empty result stops the step by default; choose Leave that field as it is to skip that field. This step does not clear fields.

Retries reuse the completed effect receipt. Matching values make no update and raise no change event. The output contains record: {type, id, number}, changed_fields and changed; it does not expose names or changed values. Test run previews field names without writing.

Changing the trigger record may start the workflow again. Matching values stop that chain with a no-op; changing values stop at the existing depth-five limit. Catalogue item and vehicle events also retain the same-workflow guard. The inspector explains this when the step targets its own changed trigger record.

History attributes updates to the workflow and records its run ID, node key and chain. Normal lifecycle events and webhooks still fire. Run logs name the changed fields, never their values.