Action overview
Understand Sanka actions and the differences between record actions, object actions, and workflow actions.
Last updated: May 10, 2026
Actions run business operations from records or workflows in Sanka. You can use them to create, update, convert, aggregate, approve, issue documents, send emails, import or export data, and sync with connected services.
Use record actions when you want to review and run one item, object actions when you want to process a selected set, and workflow actions when the work should run automatically based on timing, events, or conditions.
What is an action?
How you use an action depends on where you run it. You can run an action from one record, from selected records in an object list, or as a step inside a workflow.| Type | Where it runs | Best for | Example |
|---|---|---|---|
| Record action | One record detail page | Processing one record after reviewing its details | Create an invoice from one order |
| Object action | Object list and selected records | Processing multiple selected records together | Issue documents for multiple invoices |
| Workflow action | Action step inside a workflow | Automating work after a trigger and conditions | Create a purchase order after approval and notify the owner |
Record actions
A record action starts from one specific record. Because you run it while viewing the record detail page, it works well when you need to confirm the customer, amount, due date, line items, or status before continuing.Common uses
- Create an order from a quote.
- Create an invoice from an order.
- Issue one document.
- Send an email or update status for one record.
Setup and operating tips
- Confirm that the target record is correct before running the action.
- Check which fields will be carried into the destination record.
- For actions that create or send something, review drafts or previews before confirming when available.
Object actions
An object action runs from an object list against selected records. It is useful for monthly work, bulk document generation, batch conversion, or other operations where several records should move together.Common uses
- Create invoices from multiple orders.
- Aggregate selected records into one document.
- Send emails for selected records.
- Update a group of imported records.
Setup and operating tips
- Confirm the selected records before running the action.
- For large batches, test with a small set first.
- Check status and action history to avoid duplicate creation.
Workflow actions
A workflow action runs inside a workflow. After an event trigger, time trigger, or manual trigger starts the workflow, one or more actions can run in sequence based on conditions.Common uses
- Automatically create downstream records after a record is created or updated.
- Notify owners about due tasks or unapproved records every morning.
- Continue from approval into purchasing, invoicing, or inventory allocation.
- Import data from an integration and update Sanka records.
Setup and operating tips
- Decide the trigger first.
- Use specific conditions to avoid unnecessary runs.
- When multiple steps are chained, make clear which output from one action is used by the next action.
- After the workflow runs, review workflow history and affected records.
Common action categories
| Category | What it does |
|---|---|
| Approval | Add request, approval, rejection, and revision steps to a workflow |
| Create and update records | Create or update quotes, orders, invoices, purchase orders, bills, and other records |
| Convert and aggregate | Convert deals to quotes or orders to invoices, or combine records |
| Documents and email | Issue PDFs or documents and send them by email when needed |
| Integrations | Import, export, or sync data with connected services |
| AI and utilities | Add assistive data entry, checks, notifications, and supporting operations |
How to choose
| Goal | Use |
|---|---|
| Review and run one record | Record action |
| Process multiple selected records | Object action |
| Automate based on timing or conditions | Workflow action |
| Require human approval | Approval step in a workflow action |
| Avoid accidental sends or duplicate creation | Start with drafts, previews, and small test runs |
