Integration
Connect Balabook to Brand.dev
When something happens in Balabook, your agent does the next thing in Brand.dev. Describe it 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 Balabook and Brand.dev 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 Balabook can start in Brand.dev
When New Invoices in Balabook
then Add a monitor in Brand.dev
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 Balabook and Brand.dev
Triggers and actions 2 triggers · 43 actions
- New Invoices
Triggers when a new invoice is created.
- New Journal Entries
Triggers when a new journal entry is created.
- Add bill
Create a bill.
- Add invoice payment
Record a payment on an invoice.
- Add journal entry
Create a journal entry.
- Create Account
Creates a new account in your company.
- Create Estimate
Creates a new draft estimate in your company.
- Create Expense
Creates a new draft expense in your company.
- Create Invoice
Creates a new draft invoice in your company.
- Create Partner
Creates the partner for the company.
- Create Transaction
Creates a new draft transaction in your company.
- Delete invoice
Delete an invoice.
- Get account
Get an account with amounts.
- Get invoice
Get an invoice by id.
- Get partner
Get a partner by id.
- List accounts
List accounts.
- List bills
List bills.
- List estimates
List estimates.
- List invoices
List invoices.
- List journal entries
List journal entries.
- List transactions
List transactions.
- Update account
Update an account.
- Update estimate
Update an estimate.
- Update expense
Update an expense.
- Update invoice
Update an invoice.
- Update partner
Update a partner.
- Add a monitor
Create a website change monitor.
- Delete a collection
Delete a WebDBs data collection.
- Delete a monitor
Delete a website change monitor.
- Extract Products From a Brand's Website
Beta feature: Extract product information from a brand's website. Brand.dev will analyze the website and return a list of products with details such as name, description, image, pricing, features, and more.
- Find rows in a collection
Query rows stored in a WebDBs data collection.
- Get a batch
Retrieve a batch's status by ID.
- Get a monitor
Retrieve a website change monitor by ID.
- Get batch results
Retrieve the results of a completed batch.
- List batches
List submitted batches.
- List collections
List WebDBs data collections.
- List monitors
List website change monitors.
- Query Website Data Using AI
Use AI to extract specific data points from a brand's website. The AI will crawl the website and extract the requested information based on the provided data points.
- Retrieve Brand Data by Company Name
Retrieve brand information using a company name. This endpoint searches for the company by name and returns its brand data.
- Retrieve person
Retrieve a person's profile data.
- Retrieve Simplified Brand Data by Domain
Returns a simplified version of brand data containing only essential information: domain, title, colors, logos, and backdrops. This endpoint is optimized for faster responses and reduced data transfer.
- Run a monitor
Trigger a website change monitor to run immediately.
- Search company news
Search for recent news articles about a company or brand.
- Update a collection
Update a WebDBs data collection's configuration.
- Update a monitor
Update a website change monitor's configuration.
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 Balabook
Balabook to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Balabook to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Balabook to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Balabook to Google SheetsGoogle Sheets
Balabook to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Balabook to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Brand.dev
Questions
Balabook and Brand.dev, answered
What can start an automation from Balabook?
Any of Balabook's 2 triggers in the catalog, including New Invoices and New Journal Entries. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Brand.dev when something happens in Balabook?
Any of Brand.dev's 19 actions, including Update a collection, Update a monitor, Add a monitor and Extract Products From a Brand's Website. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Brand.dev to Balabook?
Brand.dev has no triggers in the catalog today, so automations start in Balabook. If you need the other direction, ask: your agent reads Brand.dev's API documentation and adds it.
Do I have to build a connector for Balabook or Brand.dev?
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.