Integration
Connect eSignatures and Google BigQuery
When Contract Signed fires in eSignatures, your agent runs Create Row in Google BigQuery, or New Job Completed in Google BigQuery to Add Signer in eSignatures. 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 eSignatures and Google BigQuery 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 eSignatures and Google BigQuery can do together
From eSignatures to Google BigQuery
When Contract Signed in eSignatures
then Create Row in Google BigQuery
When Contract Withdrawn in eSignatures
then Create Rows in Google BigQuery
From Google BigQuery to eSignatures
When New Job Completed in Google BigQuery
then Add Signer in eSignatures
When New Row in Google BigQuery
then Add Template in eSignatures
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 eSignatures and Google BigQuery
Triggers and actions 8 triggers · 21 actions
Trigger
Contract SignedTriggers when a contract is signed by all signers.
Trigger
Contract WithdrawnFires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn".
Trigger
Signer Declined SignatureFires when a signer declines to sign the contract. Webhook event "Signer declined the signature".
Trigger
Signer Viewed ContractFires when a signer opens/views the contract. Webhook event "Signer viewed the contract".
Action
Add SignerAdd a new signer to an existing contract.
Action
Add TemplateCreate a new reusable contract template.
Action
Create ContractCreates a new contract.
Action
Delete SignerRemove a signer from a contract that has not yet signed.
Action
Delete TemplateDelete a contract template.
Action
Get ContractRetrieve a contract's current status, signer states, and metadata.
Action
Get TemplateRetrieve a contract template's details.
Action
List TemplatesList all contract templates in the account.
Action
Send Contract DraftSend a previously created draft contract to its signers.
Action
Update TemplateUpdate an existing contract template's title or settings.
Action
Withdraw ContractWithdraw (cancel) a contract that has been sent but not fully signed.
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.
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 eSignatures
eSignatures to PexafySemantic image search across 9+ free stock photo sources with a unified JSON schema
eSignatures to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
eSignatures to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
eSignatures to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
eSignatures to Google SheetsGoogle Sheets
eSignatures to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Google BigQuery
Gmail to Google BigQueryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
ActiveCampaign to Google BigQueryActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to Google BigQueryOrganize anything with Airtable, a modern database created for everyone.
Asana to Google BigQueryAsana is a collaborative information manager for workspace.
ClickUp to Google BigQueryClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to Google BigQueryDiscord is an all-in-one voice and text chat for gamers.
Questions
eSignatures and Google BigQuery, answered
What can start an automation from eSignatures?
Any of eSignatures's 4 triggers in the catalog, including Contract Signed, Contract Withdrawn, Signer Declined Signature and Signer Viewed Contract. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Google BigQuery when something happens in eSignatures?
Any of Google BigQuery's 10 actions, including Create Row, Create Rows, Get Rows for Job Completed and Update Row(s). Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Google BigQuery to eSignatures?
Yes. When something happens in Google BigQuery, your agent can act in eSignatures too. This page covers both directions: Google BigQuery's triggers and eSignatures's actions are listed here as well.
Do I have to build a connector for eSignatures or Google BigQuery?
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.