STEP 1
Select MarketProvider in workflow
Pick MarketProvider app in the workflow builder [4] - just one click to select the app.
MarketProvider Integration
Product catalog and marketplace data provider for categories, products, and catalog requests. Connect MarketProvider campaigns and audiences to CRM, advertising, and analytics workflows. When Get a Catalog arrives, automatically continue with Get a Product by ID or Get a Request Product.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for MarketProvider integration
Triggers can detect changes in MarketProvider and run actions that can create, search or modify data inside MarketProvider automatically [3] — exactly how you set them.
- Get a CatalogRetrieves information for a single catalog.
- Get a Product by IDGets a product by its ID from multiple catalogs.
- Get a Product by IDRetrieves a product by ID from a specific catalog.
- Get a Request ProductRetrieves information about a request product within a specified catalog.
- Get a Request ProductRetrieves a request product from multiple catalogs.
- Get Account InformationRetrieves account information.
- Get Category Product Full InformationRetrieves full information for category products across multiple catalogs.
- Get Category ProductsRetrieves full information about category products including one catalog.
- Get Category ProductsGets a category product's brief information from multiple catalogs.
- Get Channel Unload ResultRetrieves the result of a channel unload for multiple catalogs.
- Get RequestGets a request from a multiple catalog.
- List Available CatalogsRetrieves a list of available catalogs.
- List CategoriesGets a category list by catalog, including multiple catalogs.
- List CategoriesLists categories within a single catalog.
- List Category ProductsRetrieves brief information about category products, including one catalog.
- Create a Multiple Catalog RequestCreates a request for multiple catalogs.
- Create a RequestCreates a request with one product in the system.
- Make an API CallPerforms an arbitrary authorized API call.
- Update a RequestUpdates a request in a multiple catalog system.
- Update a Request with a CatalogUpdates a request using a specified catalog.
How to integrate MarketProvider in automation workflow?
3 simple steps to make your MarketProvider connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect MarketProvider
When prompted, authorize access to MarketProvider in WEXTL once. MarketProvider credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your MarketProvider account. Approve?
STEP 3
Build a workflow
Build your workflow with MarketProvider yourself or with WEXTL® AI Builder. Connect MarketProvider to any available integrations [5], or use HTTP node to go beyond them.
MarketProvider
How MarketProvider connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever MarketProvider app is called in workflows. That allows your marketing automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that MarketProvider supports.
The following table illustrates what fields MarketProvider integration require during authorization flow inside our workflow builder [4].
Video slide demonstrates how MarketProvider is connected in WEXTL builder [4].
| Field | Type | Help |
|---|---|---|
API KeyRequired | password | The API key is gotten from https://my.marketprovider.com/my-cabinet/tokens after logging in. |
Connect MarketProvider to popular apps on WEXTL
Enter a name of the other app you want to sync with MarketProvider below. Click on selected app to explore integration options with MarketProvider. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with MarketProvider integration
Select Get Category Product Full Information action from MarketProvider - this will be a starting point in your automation. Whenever event happens in MarketProvider, workflow will start [7] from Get Category Product Full Information node.
Search for Get a Product by ID, connect it as the next step of integration sequence. You can use filters between Get Category Product Full Information and Get a Product by ID, so only important data pass from Get Category Product Full Information to the next step. WEXTL gives you full control over the process of MarketProvider automation. All parts of workflow are visible on the canvas [4].
MarketProvider on WEXTL has 22 modules for combining marketing automations. Explore MarketProvider documentation for more.
Video slide demonstrates how Get Category Product Full Information and Get a Product by ID [6] nodes are used in MarketProvider workflow.
Frequently asked questions
Common questions about automating MarketProvider in your workflows.
MarketProvider has no triggers, but it provides 22 actions including "Get a Catalog", "Get a Product by ID", and "Get a Product by ID". Pair them with triggers from other apps to automate MarketProvider tasks.
Integration has 22 actions, including "Get a Catalog", "Get a Product by ID", and "Get a Product by ID", and more. Refer to our MarketProvider Documentation for detailed inputs and outputs.
No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The MarketProvider integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by MarketProvider official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where MarketProvider provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever MarketProvider or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for MarketProvider inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with MarketProvider modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the MarketProvider integration.
- MarketProvider integration source code, module specs and credentials implementation.
- Internal MarketProvider integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official MarketProvider vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® MarketProvider App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation