---
title: "Connect HelloSign and QuickBase - APIANT.ai"
description: "When \"New Signature Request\" fires in HelloSign, your agent runs \"Insert or update records\" in QuickBase."
canonical: "https://apiant.ai/connect/hellosign-to-quickbase"
---

# Connect HelloSign and QuickBase

When **New Signature Request** fires in [HelloSign](https://apiant.ai/connections/hellosign), your agent runs **Insert or update records** in [QuickBase](https://apiant.ai/connections/quickbase), or **New or updated record** in QuickBase to **Get Signature Request Files** in HelloSign. Describe the whole flow and it is built, tested on every scenario and kept running.

HelloSign **1** trigger HelloSign **8** actions QuickBase **2** triggers QuickBase **21** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want HelloSign and QuickBase to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

QuickBase holds the records your team works from, and HelloSign handles the signing. Joining them means a contract row in QuickBase can send its own signature request, and a new request in HelloSign can be written back to the right QuickBase record so the table shows where each document stands.

Example flows

## What HelloSign and QuickBase can do together

### From HelloSign to QuickBase

- When **New Signature Request** in HelloSign then **Insert or update records** in QuickBase
- When **New Signature Request** in HelloSign then **Query records** in QuickBase

### From QuickBase to HelloSign

- When **New or updated record** in QuickBase then **Get Signature Request Files** in HelloSign
- When **New record** in QuickBase then **Cancel Signature Request** in HelloSign

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 HelloSign and QuickBase

## Triggers and actions 3 triggers · 29 actions

- Trigger

**New Signature Request**

Triggers when a new signature request appears in the account.

- Action

**Cancel Signature Request**

Cancels an incomplete signature request.

- Action

**Get Account**

Returns information about the current Dropbox Sign account.

- Action

**Get Signature Request**

Retrieves a single signature request by its ID.

- Action

**Get Signature Request Files**

Returns a download URL for the documents of a signature request as a PDF.

- Action

**List Signature Requests**

Lists signature requests for the account, paginated and ordered newest first.

- Action

**List Templates**

Lists the reusable templates available to the account.

- Action

**Send Reminder**

Sends an email reminder to a signer to sign a pending signature request.

- Action

**Send Signature Request**

Creates and sends a new signature request using document file URLs and a list of signers.

- Trigger

**New or updated record**

Polling trigger. Fires for each record added or modified in the specified Quickbase table, ordered by Date Modified. Records are deduped by their Record ID# (field 3).

- Trigger

**New record**

Polling trigger. Fires for each new record added to the specified Quickbase table, ordered by Record ID#. Records are deduped by their Record ID# (field 3).

- Action

**Add app**

Creates a new Quickbase application in the connected realm, optionally with a description, app variables and security properties.

- Action

**Add field**

Creates a new field in a Quickbase table, optionally with display settings, type-specific properties and per-role permissions.

- Action

**Add table**

Create a new table in a QuickBase app.

- Action

**Delete app**

Delete a QuickBase app by id.

- Action

**Delete field**

Delete one or more QuickBase fields from a table.

- Action

**Delete records**

Delete records from a Quickbase table that match a query (Quickbase query language in the where clause).

- Action

**Delete table**

Deletes a table from a Quickbase app, including all of the data within it.

- Action

**Get app**

Get the properties of a Quickbase application by its app ID.

- Action

**Get field**

Get a single QuickBase field by id.

- Action

**Get report**

Get metadata for a single QuickBase report.

- Action

**Get table**

Get the properties of a single Quickbase table by table ID and app ID.

- Action

**Get table fields**

List all fields (columns) for a Quickbase table, including field IDs, labels, and types.

- Action

**Get tables for app**

List all tables belonging to a Quickbase application.

- Action

**Insert or update records**

Insert new records or update existing ones in a Quickbase table. Pass data as an array of record objects keyed by field ID. Include the table's key field (or record ID field 3) to update; omit to insert.

- Action

**List reports**

Lists all reports defined on a Quickbase table.

- Action

**Query records**

Query records from a Quickbase table. Optionally pass select (array of field IDs), where (Quickbase query language), sortBy, groupBy, and options (skip/top).

- Action

**Run formula**

Runs a Quickbase formula against a table (and optionally a record) and returns the result as text.

- Action

**Run report**

Run a Quickbase report by report ID and table ID and return its result rows.

- Action

**Update app**

Updates an app's name, description, app variables and/or security properties. Properties left blank stay unchanged.

- Action

**Update field**

Updates the properties and per-role permissions of an existing field in a Quickbase table. Properties left blank stay unchanged.

- Action

**Update table**

Update an existing QuickBase table's properties.

## Each app on its own

- [ **HelloSign** Dropbox Sign (formerly HelloSign) e-signature platform.](https://apiant.ai/connections/hellosign)
- [ **QuickBase** Quickbase is a low-code database platform. Build and automate against Quickbase apps, tables, and records.](https://apiant.ai/connections/quickbase)

Reviews

## What our customers say

## More from HelloSign

- [ **HelloSign to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/hellosign-to-salesforce)
- [ **HelloSign to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/hellosign-to-slack)
- [ **HelloSign to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/hellosign-to-mailchimp)
- [ **HelloSign to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/hellosign-to-shopify)
- [ **HelloSign to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/hellosign-to-trello)
- [ **HelloSign to JIRA** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/hellosign-to-jira)

## More into QuickBase

- [ **HubSpot to QuickBase** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-quickbase)
- [ **Mailchimp to QuickBase** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-quickbase)
- [ **Pipedrive to QuickBase** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-quickbase)
- [ **JIRA to QuickBase** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/jira-to-quickbase)
- [ **Klaviyo to QuickBase** Klaviyo is a marketing automation platform for email and SMS.](https://apiant.ai/connect/klaviyo-to-quickbase)
- [ **JotForm to QuickBase** JotForm is a web-based WYSIWYG form builder. Create forms, integrate them into your site, and collect...](https://apiant.ai/connect/jotform-to-quickbase)

Questions

## HelloSign and QuickBase, answered

###

### Can a signature request be sent straight from a QuickBase record?

Yes. A new record in QuickBase can trigger a send signature request in HelloSign using the signer details on that record, and the request details can then be written back with insert or update records.

###

### What happens in QuickBase when a signature request shows up in HelloSign?

The new signature request trigger in HelloSign can query records in QuickBase to find the matching row by signer email. From there it can insert or update records so the request ID and status sit on that record.

###

### What can start an automation from HelloSign?

Any of HelloSign's 1 trigger in the catalog, including New Signature Request. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in QuickBase when something happens in HelloSign?

Any of QuickBase's 21 actions, including Insert or update records, Query records, Update app and Update field. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from QuickBase to HelloSign?

Yes. When something happens in QuickBase, your agent can act in HelloSign too. This page covers both directions: QuickBase's triggers and HelloSign's actions are listed here as well.

###

### Do I have to build a connector for HelloSign or QuickBase?

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 HelloSign and QuickBase 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.
