---
title: "Connect Gridfox to MarketProvider - APIANT.ai"
description: "When \"Record Created\" fires in Gridfox, your agent runs \"Add attribute\" in MarketProvider."
canonical: "https://apiant.ai/connect/gridfox-to-marketprovider"
---

# Connect Gridfox to MarketProvider

When **Record Created** fires in [Gridfox](https://apiant.ai/connections/gridfox), your agent runs **Add attribute** in [MarketProvider](https://apiant.ai/connections/marketprovider). Describe the whole flow and it is built, tested on every scenario and kept running.

Gridfox **2** triggers Gridfox **9** actions MarketProvider **7** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Gridfox and MarketProvider to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Gridfox can start in MarketProvider

- When **Record Created** in Gridfox then **Add attribute** in MarketProvider
- When **Record Created or Updated** in Gridfox then **Add category** in MarketProvider

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Gridfox and MarketProvider

## Triggers and actions 2 triggers · 16 actions

- Trigger

**Record Created**

Triggers when a new record is created.

- Trigger

**Record Created or Updated**

Fires when a record in the chosen Gridfox table is created or updated.

- Action

**Add record**

Create a record in a table.

- Action

**Add user**

Add a user to the project.

- Action

**Delete record**

Delete a record.

- Action

**Find records**

Search records in a table by search parameters.

- Action

**Get record**

Get a record by reference field value.

- Action

**Get record audit**

Get audit history for a record.

- Action

**List tables**

List tables in the project.

- Action

**List User Groups**

lists the project's user groups with their member users (id, email).

- Action

**Update record**

Update a record by reference field value.

- Action

**Add attribute**

Creates a new attribute in a MarketProvider catalog, such as a text, number, or list-select product characteristic.

- Action

**Add category**

Creates a new category in a MarketProvider catalog, optionally nested under a parent category.

- Action

**Add group**

Creates a new attribute group in a MarketProvider catalog and returns the created group.

- Action

**List attributes**

Returns the attributes defined in a catalog, optionally filtered by name, type, group, category or id.

- Action

**List catalogs**

Returns every catalog available to your MarketProvider account, with each catalog's id and name.

- Action

**List categories**

Returns the categories in a MarketProvider catalog, optionally filtered by name, level, parent category or status.

- Action

**List groups**

Returns the attribute groups in a catalog, optionally filtered by name, comment, master flag or whether they have attributes.

## Each app on its own

- [ **Gridfox** Manage your work, your way with Gridfox. The tool for team collaboration that helps you build custom...](https://apiant.ai/connections/gridfox)
- [ **MarketProvider** MarketProvider is a PIM system that helps manage, enrich, and share product data across channels.](https://apiant.ai/connections/marketprovider)

Reviews

## What our customers say

## More from Gridfox

- [ **Gridfox to Checkly** Synthetic monitoring platform for uptime, API, and browser checks with alerting and status pages.](https://apiant.ai/connect/gridfox-to-checkly)
- [ **Gridfox to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/gridfox-to-hubspot)
- [ **Gridfox to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/gridfox-to-salesforce)
- [ **Gridfox to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/gridfox-to-slack)
- [ **Gridfox to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/gridfox-to-mailchimp)
- [ **Gridfox to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/gridfox-to-stripe)

## More into MarketProvider

- [ **HubSpot to MarketProvider** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-marketprovider)
- [ **Salesforce to MarketProvider** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-marketprovider)
- [ **Slack to MarketProvider** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-marketprovider)
- [ **Google Sheets to MarketProvider** Google Sheets](https://apiant.ai/connect/google-sheets-to-marketprovider)
- [ **Gmail to MarketProvider** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-marketprovider)
- [ **Google Calendar to MarketProvider** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-marketprovider)

Questions

## Gridfox and MarketProvider, answered

###

### What can start an automation from Gridfox?

Any of Gridfox's 2 triggers in the catalog, including Record Created and Record Created or Updated. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in MarketProvider when something happens in Gridfox?

Any of MarketProvider's 7 actions, including Add attribute, Add category, Add group and List attributes. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from MarketProvider to Gridfox?

MarketProvider has no triggers in the catalog today, so automations start in Gridfox. If you need the other direction, ask: your agent reads MarketProvider's API documentation and adds it.

###

### Do I have to build a connector for Gridfox or MarketProvider?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Gridfox and MarketProvider without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
