Integration
Connect oboloo to Workato Api Proxy
When Contract Updated fires in oboloo, your agent runs Update recipe in Workato Api Proxy. 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 oboloo and Workato Api Proxy to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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)Example flows
What oboloo can start in Workato Api Proxy
When Contract Updated in oboloo
then Update recipe in Workato Api Proxy
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 oboloo and Workato Api Proxy
Triggers and actions 5 triggers · 21 actions
- Contract Updated
Triggers when a contract is updated in oboloo.
- New Contract
Triggers when a new contract record is created.
- New Supplier
Triggers when a new supplier record is created.
- Saving Record Is Created or Updated in Oboloo
Triggers when a savings record is created or updated in oboloo.
- Supplier Updated
Triggers when a supplier record is updated.
- Add department
/api/departments/add - create a department.
- Add location
/api/locations/add - add or update a location.
- Add saving
/api/savings/add - create a new saving entry.
- Add savings milestone
/api/savings/milestones/add - add a milestone to a saving.
- Create Contract
Create a new contract in oboloo
- Create New Supplier
Creates a new supplier record in oboloo
- Get supplier address
/api/getSupplierAddress/{id} - supplier address by id.
- List contracts
/api/contracts - paginated list of contracts with filters.
- List departments
/api/getAllDepartments - departments and department locations.
- List locations
/api/getAllLocations - all locations.
- List savings
/api/savings - list savings with multiple filters.
- List suppliers
/api/suppliers - paginated list of suppliers with filters.
- Update a Contract in Oboloo
Update a contract record in oboloo
- Update a Supplier in Oboloo
Updates an existing Supplier record in oboloo
- Update saving
/api/savings/update - update a saving.
- Update supplier address
/api/suppliers/update/address - update a supplier address.
- Get job
Returns one job run of a recipe, including its status, timing, error details and the input and output of each step.
- Get recipe
Returns the details of a Workato recipe, including its name, status, connections and step definitions.
- List jobs
Returns the jobs run by a recipe, up to 1,000 at a time, along with succeeded and failed job counts.
- Start recipe
Starts a stopped Workato recipe so it begins processing trigger events.
- Update recipe
Updates an existing stopped recipe's name, steps, connections, folder or description. Running recipes cannot be updated.
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 oboloo
oboloo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
oboloo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
oboloo to StripeStripe is a payment processing platform for online businesses.
oboloo to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
oboloo to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
oboloo to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Workato Api Proxy
HubSpot to Workato Api ProxyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Workato Api ProxyGoogle Sheets
Gmail to Workato Api ProxyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Workato Api ProxyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
oboloo and Workato Api Proxy, answered
What can start an automation from oboloo?
Any of oboloo's 5 triggers in the catalog, including Contract Updated, New Contract, New Supplier and Saving Record Is Created or Updated in Oboloo. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Workato Api Proxy when something happens in oboloo?
Any of Workato Api Proxy's 5 actions, including Update recipe, Get job, Get recipe and List jobs. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Workato Api Proxy to oboloo?
Workato Api Proxy has no triggers in the catalog today, so automations start in oboloo. If you need the other direction, ask: your agent reads Workato Api Proxy's API documentation and adds it.
Do I have to build a connector for oboloo or Workato Api Proxy?
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.
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.