Magento
Magento (Adobe Commerce) order and shipment actions
Magento (now Adobe Commerce) is the open-source enterprise e-commerce platform, and Tiny Command exposes seven actions against the Magento 2 REST API — there are no native triggers because Magento doesn't emit outbound webhooks in the core (the Magento_WebApi module is read/write only). For event-driven workflows, the standard pattern is to schedule Search Orders against a "created after" timestamp every 1–5 minutes and dedupe on order increment ID. The action surface covers the operational fulfilment cycle: Search Orders with full Magento query syntax (searchCriteria filter groups support every order attribute), Get Order (single fetch with line items, customer, shipping, billing), Get Customer, Create Invoice (full or partial), Create Shipment with tracking, Ship Order (the convenience action that auto-invoices and ships in one call when payment_action is sale), and Cancel Order. Magento auth uses an admin integration token rather than per-user OAuth — set up once in Magento admin, used for every action.
Do anything Magento can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Cancel Magento Order | Cancels an order in Magento. For "fraud detection flagged → auto-cancel" or "customer requested → cancel + refund" workflows. |
| Create Magento Invoice | Creates an invoice for an order — full or partial line quantities. The first step before Create Shipment for the standard fulfilment flow. |
| Create Magento Shipment | Creates a shipment against an invoiced order with carrier and tracking number. For "external fulfilment confirms shipment → update Magento" workflows. |
| Get Magento Customer | Returns a customer by ID with addresses, group, recent orders. The standard lookup for customer-context workflows. |
| Get Magento Order | Returns an order by ID with line items, customer, shipping/billing addresses, status. The lookup for fulfilment workflows that need richer order context. |
| Search Magento Orders | Uses Magento's searchCriteria DSL — filterGroups with filters of field/condition_type/value. For "all orders created after X with status processing" polling workflows (since Magento doesn't emit native order webhooks). |
| Ship Magento Order | Convenience action — auto-invoices (if not already) and fully ships the order with tracking attached. For "external fulfilment ready → close out the order in Magento" simple workflows. |
Pre-built Magento workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Magento once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Magento field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Magento integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Magento to Tiny Command?
What Magento triggers does Tiny Command support?
What Magento actions can I run from a workflow?
Is the Magento integration real-time?
Do I need to write code to use Magento with Tiny Command?
How much does the Magento integration cost?
More e-commerce apps people connect.
Same category as Magento, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Magento.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
