Integration
Connect Nozbe to Catalog Machine
When New Task fires in Nozbe, your agent runs Delete product in Catalog Machine. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Nozbe and Catalog Machine to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Nozbe is where the work gets tracked and Catalog Machine is where the product data lives. Connecting them lets a task in Nozbe drive real catalog work: looking up a product by its code, updating its fields, importing a CSV, re-pulling Shopify products, or removing a discontinued item, with the result written back as a comment on the task.
Example flows
What Nozbe can start in Catalog Machine
When New Task in Nozbe
then Delete product in Catalog Machine
When Updated Task in Nozbe
then Get product in Catalog Machine
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 Nozbe and Catalog Machine
Triggers and actions 2 triggers · 16 actions
Trigger
New TaskTriggers when a new task is created.
Trigger
Updated TaskTriggers when a task is updated.
Action
Create AttachmentCreates a new Attachment
Action
Create CommentCreates a new Comment
Action
Create ProjectCreates a new Project
Action
Create TaskCreates a new Task or imports many from CSV file
Action
Find Task by IDFinds a task based on id.
Action
Find Task by NameFinds a task based on name.
Action
Get CommentReturns one comment by id.
Action
Get ProjectReturns one project by id.
Action
Update TaskUpdates the Task
Action
Delete productDeletes a product from your Catalog Machine account by its product code.
Action
Get productReturns a single product by its code, including all product fields, variants and collections.
Action
Get Product Import StatusReturns the current status and any errors of the most recent product import job (CSV import or Shopify sync).
Action
Import Product CSVImports products into Catalog Machine from a CSV file at a public URL and returns the import job id. Products with formatting errors are skipped.
Action
List categoriesReturns all product categories in your Catalog Machine account, including the fields each category defines.
Action
Save ProductUpdates an existing product in Catalog Machine by its product code, changing only the fields you fill in.
Action
Sync Shopify ProductsRe-imports products that already exist in Catalog Machine from the connected Shopify store, updating their prices, images, variants and other fields. Returns the id of the import job.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Nozbe
Nozbe to ClearBounceClearBounce is a real-time email verification service that reduces bounces, protects sender reputation, and...
Nozbe to Contact Form 7Contact Form 7 can manage multiple contact forms, plus you can customise the form and the mail contents...
Nozbe to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Nozbe to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Nozbe to StripeStripe is a payment processing platform for online businesses.
Nozbe to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Catalog Machine
HubSpot to Catalog MachineHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Catalog MachineSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Catalog MachineSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Catalog MachineGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Catalog MachineGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Catalog MachineGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Nozbe and Catalog Machine, answered
Can a change in Catalog Machine start the automation?
No. Catalog Machine has no triggers here, so every run starts in Nozbe with a New Task or an Updated Task. Catalog Machine comes in on the action side, through steps like Get product, Save Product, Import Product CSV or Delete product.
What happens if the product code on the task is not in Catalog Machine?
The agent uses Get product first and only runs Save Product when that product comes back. If nothing is found, it writes a comment on the Nozbe task instead, and it tests every scenario before the setup goes live.
What can start an automation from Nozbe?
Any of Nozbe's 2 triggers in the catalog, including New Task and Updated Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Catalog Machine when something happens in Nozbe?
Any of Catalog Machine's 7 actions, including Delete product, Get product, Get Product Import Status and Import Product CSV . Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Catalog Machine to Nozbe?
Catalog Machine has no triggers in the catalog today, so automations start in Nozbe. If you need the other direction, ask: your agent reads Catalog Machine's API documentation and adds it.
Do I have to build a connector for Nozbe or Catalog Machine?
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 Nozbe and Catalog Machine 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.