---
title: "Connect Pics.io to SigningHub - APIANT.ai"
description: "When \"Assets Added to Collection\" fires in Pics.io, your agent runs \"Add Document\" in SigningHub."
canonical: "https://apiant.ai/connect/pics-io-to-signinghub"
---

# Connect Pics.io to SigningHub

When **Assets Added to Collection** fires in [Pics.io](https://apiant.ai/connections/pics-io), your agent runs **Add Document** in [SigningHub](https://apiant.ai/connections/signinghub). Describe the whole flow and it is built, tested on every scenario and kept running.

Pics.io **10** triggers Pics.io **11** actions SigningHub **11** actions

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

## What do you want Pics.io and SigningHub 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)

Example flows

## What Pics.io can start in SigningHub

- When **Assets Added to Collection** in Pics.io then **Add Document** in SigningHub
- When **Assets Color Changed** in Pics.io then **Add User** in SigningHub

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 Pics.io and SigningHub

## Triggers and actions 10 triggers · 22 actions

- Trigger

**Assets Added to Collection**

Triggers when an asset is added to the selected Pics.io collection (including its nested collections).

- Trigger

**Assets Color Changed**

Triggers when the color label on an asset in your Pics.io library is set or changed.

- Trigger

**Assets Flag Changed**

Triggers when an asset's flag changes to flagged, unflagged or rejected in your Pics.io library.

- Trigger

**Assets Metadata Changed**

Triggers when an asset's metadata (title, description, keywords, custom fields and other details) is changed in Pics.io.

- Trigger

**Assets Moved to Collection**

Triggers when assets are moved into the chosen collection (or any collection inside it).

- Trigger

**Assets Raiting Changed**

Triggers when an asset's star rating is changed in your Pics.io library.

- Trigger

**Metadata Processing Completed**

Triggers when Pics.io finishes processing an asset's file metadata, including when metadata is reprocessed for an existing asset.

- Trigger

**New Asset**

Triggers when a new asset is added to your Pics.io library, optionally limited to a collection, inbox, lightboard, type or other filters.

- Trigger

**New Collection**

Triggers when a new collection is created directly inside the collection you choose (pick the root to watch top-level collections).

- Trigger

**New Comment**

Triggers when a new comment is added to an asset in your Pics.io library.

- Action

**Add assets to collection**

Adds one or more Pics.io assets to a collection, or moves them into it so they leave their other collections.

- Action

**Add keyword**

Creates a new keyword in the Pics.io keyword tree, optionally nested under a parent keyword.

- Action

**Create Collection**

Creates a new collection in Pics.io, optionally nested inside an existing parent collection.

- Action

**Delete collection**

Deletes a collection from your Pics.io library.

- Action

**Find assets**

Returns the assets in your Pics.io library that match a text search and optional filters such as collection, type, flag, rating, color or creation date.

- Action

**Find collections**

Returns the collections whose name or description contains the text you search for.

- Action

**Find keywords**

Returns the keywords in your Pics.io account whose name matches the search text.

- Action

**Get assets**

Returns the full details of one or more Pics.io assets by their IDs.

- Action

**List custom fields**

Returns every custom field defined in your Pics.io workspace, including each field's title, type, visibility and allowed options.

- Action

**Update asset**

Updates an existing Pics.io asset by ID — its file name, title, description, rating, flag and color label — and returns the updated asset. Fields left blank are not changed.

- Action

**Update custom field values on assets**

Sets the value of one custom field on one or more Pics.io assets at once.

- Action

**Add Digital Signature**

Adds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow.

- Action

**Add Document**

Uploads a document file into an existing SigningHub document package.

- Action

**Add Electronic Signature**

Adds an electronic signature field to a document in a package, assigned to a recipient in the workflow.

- Action

**Add Recipient to Workflow**

Adds a signer or other recipient to a document package's workflow.

- Action

**Add User**

Registers a new user in your SigningHub enterprise account, optionally with a password, role and profile details.

- Action

**Create Integration URL**

Generates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application.

- Action

**Create Package**

Creates a new document package in SigningHub to hold documents and recipients for a signing workflow.

- Action

**Download Package**

Downloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents.

- Action

**Get Document Fields**

Returns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields.

- Action

**Get Package**

Returns the details of a SigningHub document package: its name, owner, status and the documents it contains.

- Action

**Share Document for Signing**

Shares a prepared document package with its signers and starts the signing workflow.

## Each app on its own

- [ **Pics.io** Pics.io is a cloud service for digital assets management built on top of Google Drive.](https://apiant.ai/connections/pics-io)
- [ **SigningHub** SigningHub is an e-signature service with a powerful workflow engine that boosts team productivity by...](https://apiant.ai/connections/signinghub)

Reviews

## What our customers say

## More from Pics.io

- [ **Pics.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pics-io-to-salesforce)
- [ **Pics.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/pics-io-to-slack)
- [ **Pics.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/pics-io-to-stripe)
- [ **Pics.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/pics-io-to-shopify)
- [ **Pics.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/pics-io-to-quickbooks-online)
- [ **Pics.io to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pics-io-to-pipedrive)

## More into SigningHub

- [ **HubSpot to SigningHub** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-signinghub)
- [ **Salesforce to SigningHub** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-signinghub)
- [ **Slack to SigningHub** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-signinghub)
- [ **Google Sheets to SigningHub** Google Sheets](https://apiant.ai/connect/google-sheets-to-signinghub)
- [ **Gmail to SigningHub** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-signinghub)
- [ **Google Calendar to SigningHub** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-signinghub)

Questions

## Pics.io and SigningHub, answered

###

### What can start an automation from Pics.io?

Any of Pics.io's 10 triggers in the catalog, including Assets Added to Collection, Assets Color Changed, Assets Flag Changed and Assets Metadata Changed. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in SigningHub when something happens in Pics.io?

Any of SigningHub's 11 actions, including Create Integration URL, Create Package, Add Digital Signature and Add Document. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from SigningHub to Pics.io?

SigningHub has no triggers in the catalog today, so automations start in Pics.io. If you need the other direction, ask: your agent reads SigningHub's API documentation and adds it.

###

### Do I have to build a connector for Pics.io or SigningHub?

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 Pics.io and SigningHub 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.
