Essential actions

Essential actions are the building blocks you reach for in almost every flow. They are deliberately generic, so you can use them across a wide range of scenarios — from quick integrations to complex, multi-step automations.

Think of them as your everyday toolbox: connect to external services, transform data, interact with Business Central records, or notify users. These actions don’t assume a specific business process. Instead, they help you model any process cleanly and reliably.

What belongs in Essentials?

Typical essential actions include:

• HTTP requests to talk to APIs and web services.
• Parsing and expressions to reshape payloads or compute values.
• Database operations to read, insert, modify, and delete records.
• Email sending to notify users or external stakeholders.

If a step is broadly useful and not tied to a single feature area, you’ll likely find it here.

When to use essential actions

Use essential actions whenever you need:

• A lightweight way to integrate with external systems.
• A safe, structured approach to manipulating data inside a flow.
• Generic utilities that support many different use cases.

They are especially helpful when you want to keep flows simple and reusable, while still covering the core mechanics of automation.

Best practices

• Keep steps small and focused: Combine essentials to build more complex behavior instead of overloading a single step.
• Validate inputs early: Parse and check data before using it in downstream actions.
• Be explicit with data access: Read and write records intentionally to avoid unexpected side effects.

Ready to explore?

Browse the pages in this section to learn how each essential action works, when to use it, and how to configure it for reliable results.