# Monta AI employee Viktor works in Monta for you. Ask in Slack or Microsoft Teams. Viktor is an AI employee that connects to Monta and helps you create shipping labels and track parcel fulfillment, running 32 Monta actions for you like Get Order, Get Return, and Cancel Order. Ask in plain English from your workspace; Viktor does the work in Monta and reports back. Viktor connects with a scoped API key. - Tool: Monta - Category: E-Commerce - Connection: API key - Actions available: 32 - Currently available in: Slack, Microsoft Teams, and Discord - Page: https://viktor.com/integrations/monta ## What can your AI employee do in Monta? Viktor connects to your Monta account and completes work in it. He doesn't just answer questions about Monta, he takes the actions on your behalf and delivers the finished result to your workspace. Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Monta actions, chains them with the other 9,800+ tools he connects to, and asks for approval before anything sensitive runs. ### About Monta The logistics service for your webshop! ### How a run works 1. **You ask in your workspace** - Describe what you need in plain English 2. **Viktor picks the actions** - Selects from 32 Monta actions, chains them together 3. **Runs in Monta** - Helps you create shipping labels and track parcel fulfillment - your real data. 4. **Reports back** - Delivers the finished result to your workspace ## Use Monta from Slack and Microsoft Teams Message Viktor in a Slack channel, a Microsoft Teams chat or a direct message. He opens Monta, does the work and posts the result in the same thread, so nobody has to switch tabs. He can also run Monta work on a schedule, like a weekly Monta summary posted to your team's channel. Anything sensitive waits for your approval before it runs. ## Security and permissions - Scoped API keys - Viktor stores your key securely, uses only the scopes you grant, and you can revoke it at any time. - Review-first approvals: sensitive Monta actions wait for your sign-off before they run. - Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models. - SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. ## What can you ask Viktor to do in Monta? - "Create shipping labels in Monta for today's orders and send me the tracking numbers." - "Compare carrier rates in Monta for this shipment and pick the cheapest option." - "Watch Monta for a delayed shipment and alert me with the tracking details." - "Pull this week's shipping costs from Monta and post them every Monday." ## How does Viktor work with Monta? 1. Open Viktor in a supported workspace. 2. Connect Monta with an API key - Viktor handles authentication. 3. Ask in plain English. Viktor runs the Monta actions, chains them with your other tools when needed, and reports back. Sensitive actions wait for your approval. ## What can Viktor do in Monta? (32 actions) - **Add Order Colli** - Register a collo (parcel) on an order, including its dimensions and tracking details. Use this to record how an order was packed; inspect the result with List Order Colli. - **Approve Inbound Forecasts** - Approve multiple inbound forecasts at once by their IDs. - **Cancel Order** - Cancel (delete) an order. Monta rejects this once picking has started (error 18), after the order has shipped (error 19), or when returns exist (error 25). - **Create Inbound Forecast Group** - Create a new inbound forecast group describing stock expected at the warehouse. Manage the group afterwards with Update Inbound Forecast Group, Get Inbound Forecast Group, or Delete Inbound Forecast Group. - **Create Order** - Create a new order in Monta for fulfillment. Provide the recipient's delivery address (which needs a Company or Last Name) and at least one order line; validate the address first with Validate Address if needed. - **Create RMA Link** - Create an RMA (return merchandise authorization) link for an order, so a customer can start a return. Review existing returns for the order with List Order Returns. - **Create Shipping Label** - Generate a shipping label for an order in a supported output format (pdf or zpl). Use this when an order is ready to ship and needs a carrier label. - **Delete Inbound Forecast Group** - Delete an inbound forecast group, or a single SKU within it when a SKU is provided. - **Download Shipping Label** - Download a single shipping label file for an order and save it to the /tmp directory. - **Forget Order** - Anonymize an order for GDPR erasure. This permanently removes personal data and cannot be undone. - **Get Inbound Forecast Group** - Retrieve an inbound forecast group and its forecasts by reference. - **Get Inbound Forecast** - Retrieve a single inbound forecast from a group by reference and SKU. - **Get Order** - Get an order by ID. - **Get Return** - Get a return by ID. - **List Inbound Forecast Events** - List inbound forecast change events created after the provided cursor ID. Use this for reliable incremental syncing of inbound forecast changes by repeatedly polling with the last event ID. - **List Inbound Forecast Groups** - List inbound forecast groups matching the provided filters. You must supply at least one filter (Created Since, Created Until, Approved, SKU, or Reference). Use this to find group references for Get Inbound Forecast Group, Update Inbound Forecast Group, or Delete Inbound Forecast Group. - **List Inbound Forecasts by Product SKU** - List all inbound forecasts for a given product SKU across groups. Use this to check expected incoming stock for a SKU. - **List Inbounds** - List inbound shipments expected at the warehouse. Use this to review incoming stock, paging forward with the Since ID cursor to walk through large result sets; relate to List Inbound Forecast Groups for grouped forecast data. - **List Order Batches** - List the batch (lot) lines shipped for an order. Use this for batch traceability when you need to know which lots were used to fulfill an order. - **List Order Colli** - List the colli (parcels) that make up an order. Use this to inspect the parcel and tracking breakdown for a shipment, for example after registering parcels with the Add Order Colli action. - **List Order Events Since ID** - List order change events created after the provided cursor ID, which is Monta's recommended method for reliable status-change polling. Use this for incremental syncing across all orders; see List Order Events for a single order's history or List Updated Orders for datetime-based bulk syncing. - **List Order Events** - List order events for an order. - **List Order ID Options** - Retrieves available options for the Order ID field. - **List Order Returns** - List the return records for an order. Use this to see all returns registered against an order. - **List Product Stock Changes** - List products whose stock changed since a specified date and time. - **List Return Forecasts** - List the expected (forecasted) returns for an order, as opposed to the actual return records from List Order Returns. Use this to anticipate inbound returns before they physically arrive. - **List Return Labels** - List the return labels for an order (labels for inbound returns), as opposed to outbound shipping labels. Use this when handling a customer return that needs a prepaid inbound label; see List Order Returns for the associated return records. - **List Shipping Labels** - List the shipping labels of an order. Use this to retrieve the label file names, typically after generating labels with Create Shipping Label. - **List Updated Orders** - List orders whose status changed since a specified date and time, including orders deleted since then. Use this for reliable bulk order syncing; for cursor-based incremental polling of individual change events, use List Order Events Since ID instead. - **Update Inbound Forecast Group** - Update an existing inbound forecast group's details by its reference: its comment, warehouse, or expected delivery date. The forecasts, supplier, and stock-allocation flag are set at creation and cannot be changed here. - **Update Order** - Change an existing order by its ID, for example to correct a customer's delivery address before it is picked. Call this directly with the order ID and the fields to change. When changing the delivery address, first read the current address with Get Order, then call this with the full address plus your change, since Monta replaces the entire address (it needs at least Street, City, and Country Code). Monta rejects address changes once picking has started (error 17) or after the order has shipped (error 19). - **Validate Address** - Validate a delivery address before submitting it, for example ahead of Create Order or Update Order. Monta returns structured error codes when the address is invalid; a complete address also needs a recipient (Company or Last Name), Postal Code, and House Number. ## Viktor uses Monta together with - [Slack](https://viktor.com/integrations/slack) - [Gmail](https://viktor.com/integrations/gmail) - [Google Sheets](https://viktor.com/integrations/google-sheets) - [HubSpot](https://viktor.com/integrations/hubspot) - [Notion](https://viktor.com/integrations/notion) - [Salesforce](https://viktor.com/integrations/salesforce) ## More E-Commerce integrations - [SureCart](https://viktor.com/integrations/surecart) - [Google BigQuery](https://viktor.com/integrations/google-bigquery) - [DataForSEO](https://viktor.com/integrations/dataforseo) - [Shopify (OAuth)](https://viktor.com/integrations/shopify) - [Facebook](https://viktor.com/integrations/facebook) - [Twilio SendGrid](https://viktor.com/integrations/twilio-sendgrid) - [Planview Leankit](https://viktor.com/integrations/planview-leankit) - [Postmark](https://viktor.com/integrations/postmark) ## FAQ ### Does Viktor integrate with Monta? Yes. Monta is one of the 9,800+ tools Viktor connects to, via a managed connector. Once connected, anyone on your team can put Viktor to work in Monta from their workspace - no workflow builder, no code. ### How do I connect Monta to Viktor? Ask Viktor in your workspace to connect Monta, then paste an API key from your Monta account when prompted. Viktor stores the key securely, uses only the scopes you grant, and you can revoke it at any time. Setup takes about two minutes. ### What can Viktor do in Monta? Viktor can run 32 Monta actions, including Get Order, Get Return, and Cancel Order - and chain them with other tools in a single request. In practice that means Viktor helps you create shipping labels and track parcel fulfillment. If a task spans several actions, Viktor plans the sequence itself and reports back when the work is done. ### Do I need to build workflows for Monta? No. Viktor isn't a workflow builder - there are no triggers to map and nothing to maintain. You ask for the outcome in plain English in your workspace, and Viktor decides which Monta actions to take, runs them, and reports back. ### Is my Monta data secure with Viktor? Yes. Viktor connects to Monta with a scoped API key, runs in an isolated environment per team, and never trains models on your data. Sensitive actions wait for your approval, and you can revoke access at any time. Viktor is SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. ### How much does the Monta integration cost? Nothing extra - every integration, including Monta, is available on every plan. You can start free with up to $100 in credits, no credit card required; the Team plan is $100 a month. ### Can Viktor use Monta together with my other tools? Yes - that's the point. Viktor connects to 9,800+ tools and works across them in a single run: he can pull data from Monta, cross-reference it with another tool - for example Slack or Gmail, and deliver the finished result in your workspace. ## Get started Viktor is free to start - up to $100 in credits, no credit card required. All 9,800+ integrations are included on every plan. Sign up at https://viktor.com or browse all integrations at https://viktor.com/integrations.