Integration
Connect Google BigQuery to Brand.dev
When New Job Completed fires in Google BigQuery, your agent runs Find rows in a collection in Brand.dev. 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 Google BigQuery 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 Google BigQuery can start in Brand.dev
When New Job Completed in Google BigQuery
then Find rows in a collection in Brand.dev
When New Row in Google BigQuery
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 Google BigQuery and Brand.dev
Triggers and actions 4 triggers · 29 actions
Trigger
New Job CompletedTriggers when a BigQuery job in the project finishes, whether it succeeded or failed.
Trigger
New RowTriggers when a new row is added to a table. New rows are detected by a column you name that increases for newer rows, such as a creation time or a sequential ID.
Trigger
Query Job Completed (With Row Data)Triggers when a SELECT query job in the project finishes successfully, and includes its result rows.
Trigger
Updated RowTriggers when a row in a table is added or changed, detected by a last-updated timestamp column you name.
Action
Create RowCreates a new row of data in a table. Note: Does not create a job.
Action
Create RowsCreates new rows of data in a table (accepts line items). Note: Does not create a job.
Action
Delete RowsDeletes every row in a table whose match column equals the value you give.
Action
Find One RowFinds the first row in a table whose column equals the value you give.
Action
Get Rows for Job CompletedReturns the result rows of a finished query job.
Action
Import DataImports a JSON, CSV, Avro or Parquet file from Cloud Storage into a table. Waits up to about 40 seconds for the import to finish; larger imports keep running in BigQuery and return state RUNNING.
Action
List DatasetsReturns the datasets in a Google Cloud project.
Action
List TablesReturns the tables in a BigQuery dataset.
Action
Run a QueryRuns a SQL query against a table in BigQuery.
Action
Update Row(s)Updates every row in a table whose match column equals the value you give, setting the columns you choose.
Action
Add a monitorCreate a website change monitor.
Action
Delete a collectionDelete a WebDBs data collection.
Action
Delete a monitorDelete a website change monitor.
Action
Extract Products From a Brand's WebsiteBeta 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.
Action
Find rows in a collectionQuery rows stored in a WebDBs data collection.
Action
Get a batchRetrieve a batch's status by ID.
Action
Get a monitorRetrieve a website change monitor by ID.
Action
Get batch resultsRetrieve the results of a completed batch.
Action
List batchesList submitted batches.
Action
List collectionsList WebDBs data collections.
Action
List monitorsList website change monitors.
Action
Query Website Data Using AIUse 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.
Action
Retrieve Brand Data by Company NameRetrieve brand information using a company name. This endpoint searches for the company by name and returns its brand data.
Action
Retrieve personRetrieve a person's profile data.
Action
Retrieve Simplified Brand Data by DomainReturns 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.
Action
Run a monitorTrigger a website change monitor to run immediately.
Action
Search company newsSearch for recent news articles about a company or brand.
Action
Update a collectionUpdate a WebDBs data collection's configuration.
Action
Update a monitorUpdate 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 Google BigQuery
Google BigQuery to HTML to ImageHTML to Image is a Powerful Image Generation API to convert HTML/CSS to Image and to take screenshots of...
Google BigQuery to PaperCleanClean document photos for printing, remove shadows, fix lighting
Google BigQuery to ResendResend is the email API for developers. It's designed for you to build, test, and send transactional and...
Google BigQuery to TypeSafeTypeSafe's Jev model answers typed questions about a piece of content and tells you how certain it is.
Google BigQuery to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Google BigQuery to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
More into Brand.dev
HubSpot to Brand.devHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Brand.devSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Brand.devSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Brand.devGoogle Sheets
Gmail to Brand.devGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Brand.devGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Google BigQuery and Brand.dev, answered
What can start an automation from Google BigQuery?
Any of Google BigQuery's 4 triggers in the catalog, including New Job Completed, New Row, Query Job Completed (With Row Data) and Updated Row. 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 Google BigQuery?
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 Google BigQuery?
Brand.dev has no triggers in the catalog today, so automations start in Google BigQuery. 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 Google BigQuery 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.