Integration
Connect Google BigQuery and Personio
When New Job Completed fires in Google BigQuery, your agent runs Add project in Personio, or Employee Updated in Personio to Create Row in Google BigQuery. 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 Personio 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)Example flows
What Google BigQuery and Personio can do together
From Google BigQuery to Personio
When New Job Completed in Google BigQuery
then Add project in Personio
When New Row in Google BigQuery
then Create Absence in Personio
From Personio to Google BigQuery
When Employee Updated in Personio
then Create Row in Google BigQuery
When Employment Updated in Personio
then Create Rows in Google BigQuery
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 Personio
Triggers and actions 11 triggers · 30 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.
Trigger
Employee UpdatedTriggers when an employee is updated.
Trigger
Employment UpdatedTriggers when one or more Employment details of a Person are updated
Trigger
New AbsenceTriggers when a new absence is created.
Trigger
New CandidateFires when a new recruiting candidate is added in Personio.
Trigger
New EmployeeTriggers when a new employee is created.
Trigger
New Employment CreatedTriggers when one or more Employment details of a Person are created
Trigger
New Open PositionTriggers when a new open position is created.
Action
Add project/v2/projects - create a project.
Action
Create AbsenceCreates a new absence.
Action
Create AttendanceCreates a new attendance.
Action
Create EmployeeCreates a new employee.
Action
Delete absence/v2/absence-periods/{id} - delete an absence period.
Action
Delete attendance/v2/attendance-periods/{id} - delete an attendance period.
Action
Delete person/v2/persons/{id} - delete a person.
Action
Find AbsenceFinds an absence by employee ID.
Action
Find EmployeeFinds a employee based on email.
Action
Find PersonFinds a person by their Personio ID, name, last name and email, optionally including their absence information.
Action
Get EmploymentRetrieves one employment of a person by id: position, status, type, working hours, org units, cost centers, supervisor, office, legal entity, dates.
Action
List absence types/v2/absence-types - list absence types.
Action
List CompensationsLists compensations filtered by person.id and a start_date/end_date window; returns id, amount, interval, type, effective_from per record.
Action
List legal entities/v2/legal-entities - list legal entities.
Action
List org units/v2/org-units - list org units.
Action
List projects/v2/projects - list projects.
Action
Update absence/v2/absence-periods/{id} - update an absence period.
Action
Update AttendanceUpdates an existing attendance.
Action
Update EmployeeUpdates an existing employee.
Action
Update Employmentupdates an employment (position, department, office, weekly hours, status, etc.); requires personio:persons:write. Fires the employment.updated webhook.
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 Personio
HubSpot to PersonioHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PersonioGoogle Sheets
Gmail to PersonioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PersonioGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PersonioGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PersonioMailchimp marketing automation and email platform.
Questions
Google BigQuery and Personio, 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 Personio when something happens in Google BigQuery?
Any of Personio's 20 actions, including Create Absence, Create Attendance, Create Employee and Update absence. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Personio to Google BigQuery?
Yes. When something happens in Personio, your agent can act in Google BigQuery too. This page covers both directions: Personio's triggers and Google BigQuery's actions are listed here as well.
Do I have to build a connector for Google BigQuery or Personio?
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 Google BigQuery and Personio 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.