Integration

Connect BigML and Teamwork

When New project fires in BigML, your agent runs List Projects in Teamwork, or New Milestone in Teamwork to Get Resource Status in BigML. 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 BigML and Teamwork to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

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)
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)

Teamwork holds the project plan and BigML holds the modelling work, and the two rarely line up on their own. Connecting them means a new BigML project can open the matching Teamwork project, task list and tasks, and Teamwork events can pull the current state of your BigML sources, datasets and models back to the people doing the work.

Example flows

What BigML and Teamwork can do together

From BigML to Teamwork

From Teamwork to BigML

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 BigML and Teamwork

Triggers and actions 7 triggers · 26 actions

Each app on its own

Reviews

What our customers say

More from BigML

More into Teamwork

Questions

BigML and Teamwork, answered

Can a new BigML project create the matching project in Teamwork?

Yes. The New project trigger in BigML can list your existing Teamwork projects first, then create the project, a task list and tasks only when nothing with that name is already there. The agent tests every scenario, including the case where the Teamwork project already exists.

What BigML information can Teamwork events pull in?

Teamwork triggers such as New Task, New Milestone or New Time Entry can call the BigML actions that list sources, datasets and models, or fetch a single resource by id to read its status and results. That information can then be written back into Teamwork as a message or task.

What can start an automation from BigML?

Any of BigML's 1 trigger in the catalog, including New project. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Teamwork when something happens in BigML?

Any of Teamwork's 22 actions, including Add Message, Create Task, List Projects and Create Project. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Teamwork to BigML?

Yes. When something happens in Teamwork, your agent can act in BigML too. This page covers both directions: Teamwork's triggers and BigML's actions are listed here as well.

Do I have to build a connector for BigML or Teamwork?

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 BigML and Teamwork 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.