One call from the product
The client asks for the business operation instead of coordinating a fragile chain of lower-level requests.
Backend actions
Give the frontend one meaningful operation.
Turn a multi-step backend job into a named action such as approve_order, invite_member, or sync_account. Daptin validates the request and runs the outcomes in order.
- Validated input
- Conditions
- HTTP + GraphQL
Business operations
Express intent, not endpoint choreography.
Declare inputs, validations, conformations, conditions, and ordered outcomes. Actions can create or change data, send mail, call integrations, work with files, and return a useful result to the client.
Permissioned like the rest of Daptin
Action execution can be restricted independently from access to the underlying records.
Database effects stay together
Database work performed in the request transaction can commit together or roll back together.
Reusable beyond one screen
Call the same action over HTTP, expose it through GraphQL, or run it from scheduled work.
Operations worth naming
Give product decisions a stable backend interface.
Approve an order
Validate the caller and current record, change related database state, and return one outcome to the frontend.
Invite a member
Create the relationship, prepare the message, and expose one permissioned operation instead of several client-side calls.
Synchronize an account
Use the signed-in user's connected provider token and map external results into application records.
Generate a report
Accept typed parameters, query the relevant data, create an asset, and invoke the same operation immediately or on a schedule.
Execution behavior
Database atomicity has a clear edge.
Inputs can be validated and conformed before ordered outcomes run. Database effects using the request transaction normally commit or roll back together. Execute permission remains distinct from permission to read the target record.
An HTTP request, sent email, or provider mutation cannot be rolled
back by a SQL transaction. Design those effects for retries and
partial failure, and use ContinueOnError only when
continuing is genuinely safe.
Product evidence
See named operations beside the data they change.
The dashboard exposes configured actions for inspection and testing. Confirm the input contract and caller permissions there, then exercise the same operation through the interface your application will use, including an expected refusal.
Build and test an action →