Magento is a self-hosted e-commerce platform used by mid-market and enterprise retailers running custom storefronts. Connecting Magento to Parabola lets ops, finance, and merchandising teams pull orders, customers, and product data into the same flows used for accounting, fulfillment, and multi-channel reporting, without manual CSV exports or engineering involvement.Documentation Index
Fetch the complete documentation index at: https://parabola.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Pull from Magento
The Pull from Magento step pulls live data from your Magento instance via the SOAP/XML API. You select a dataset (Sales Orders, Customers, or Products) and a date range, and Parabola brings the records into your flow for cleaning, joining, and routing.How to authenticate
Magento authentication has two parts: creating a SOAP/XML role, then creating a SOAP/XML user that uses that role.Create a SOAP/XML role
Create a SOAP/XML user
Connect in Parabola
Provide the following five fields:
- Host — your Magento domain without
http://orhttps:// - Port — typically
80for non-SSL or443for SSL - API Path — the path to the XML-RPC API, including the leading
/ - API Username — the user name you set on the SOAP/XML user
- API Key — the API key you set on the SOAP/XML user
Configure your settings
Once connected, the Pull from Magento step lets you choose:- Dataset — Sales Orders, Customers, or Products.
- Created — a date range to filter the pull. Use the shortest window that still covers the data you need to keep runs fast.
Available data
The native Pull from Magento step exposes three datasets:- Sales Orders — order ID, increment ID, customer info, line items (product, SKU, quantity, price), shipping and billing addresses, totals, taxes, status, and timestamps. Filter by created date.
- Customers — customer ID, name, email, group, store ID, billing and shipping addresses, account creation and update timestamps.
- Products — product ID, SKU, name, type, status, visibility, attribute set, pricing, and inventory attributes for catalog items.
Common use cases
- Reconcile Magento orders against payments: Join Magento sales orders with Stripe charges or Square payments so finance can confirm captured revenue matches fulfilled orders.
- Combine Magento with other channels: Union Magento orders with Shopify, Amazon Seller Central, and Walmart into a single multi-channel sales report for executive reporting.
- Push orders into accounting: Send daily Magento revenue, refunds, and tax breakdowns into NetSuite or QuickBooks Online for a clean monthly close.
- Send fulfillment files to your 3PL: Build a clean order CSV from Magento and drop it on an FTP server, Google Drive folder, or warehouse system like ShipBob or ShipHero.
- Sync customer data to marketing: Push new and updated Magento customers into Klaviyo, Mailchimp, HubSpot, or Salesforce so marketing and sales work from current data.
- Trigger ops alerts on inventory or order anomalies: Send a Slack message when a high-value order comes in, when a SKU drops below a stock threshold, or when refund volume spikes.
Tips for using Parabola with Magento
- Strip the protocol from your host. Magento’s SOAP/XML auth fails if the Host field includes
http://orhttps://. Use the bare domain. - Match the port to your protocol. Use
443for HTTPS Magento installs and80for plain HTTP. Mismatched ports are a common cause of connection failures. - Filter by created date in the step. Pulling “all sales orders” on a multi-year Magento store gets slow. Start with the last 7 or 30 days and extend only if you need historical reporting.
- Use Pull from an API for richer order detail. The native step gives you order headers and high-level customer and product fields. For invoices, shipments, custom attributes, and EAV data, use Pull from an API with the same credentials.
- Match cadence to use case. Hourly for ops dashboards, daily for finance reconciliation, weekly for category and customer cohort reporting.
- Document your flows. Magento’s data model is dense and customizable per store. Add notes to each step so the next person can audit and maintain the flow.
FAQ
Does Parabola support Magento 1 and Magento 2?
The native Pull from Magento step uses the SOAP/XML API, which is supported across Magento installs that have it enabled. For Magento 2 stores using the REST API exclusively, use the Pull from an API step with your Magento 2 token.Can I push data back into Magento?
The native step is read-only. To create or update orders, customers, or products in Magento, use a Send to an API step pointed at the relevant Magento endpoint with your credentials.Why does my connection keep failing?
The three most common causes:- The Host field includes
http://orhttps://. Remove the protocol. - The Port doesn’t match the protocol (use
443for SSL). - The API Path is missing the leading
/.
Can I pull custom attributes or EAV data?
Not from the native step. Use Pull from an API against the Magento REST or SOAP endpoint that exposes the attribute you need, authenticated with the same SOAP/XML credentials.With Magento and Parabola connected, the order, customer, and product exports your team rebuilds every week run on a schedule, with clean data flowing into the systems where finance, fulfillment, and marketing actually work.