Integration
Connect HelloSign and PubNub
When New Signature Request fires in HelloSign, your agent runs Publish Message in PubNub, or New Message on Channel in PubNub to Get Signature Request Files in HelloSign. 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 HelloSign and PubNub 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 HelloSign and PubNub can do together
From HelloSign to PubNub
When New Signature Request in HelloSign
then Publish Message in PubNub
When New Signature Request in HelloSign
then Update channel metadata in PubNub
From PubNub to HelloSign
When New Message on Channel in PubNub
then Get Signature Request Files in HelloSign
When Presence Change on Channel in PubNub
then Send Reminder 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 PubNub
Triggers and actions 3 triggers · 17 actions
Trigger
New Signature RequestTriggers when a new signature request appears in the account.
Action
Cancel Signature RequestCancels an incomplete signature request.
Action
Get AccountReturns information about the current Dropbox Sign account.
Action
Get Signature RequestRetrieves a single signature request by its ID.
Action
Get Signature Request FilesReturns a download URL for the documents of a signature request as a PDF.
Action
List Signature RequestsLists signature requests for the account, paginated and ordered newest first.
Action
List TemplatesLists the reusable templates available to the account.
Action
Send ReminderSends an email reminder to a signer to sign a pending signature request.
Action
Send Signature RequestCreates and sends a new signature request using document file URLs and a list of signers.
Trigger
New Message on ChannelTriggers when a new message is published to a PubNub channel.
Trigger
Presence Change on ChannelFires when a user appears on a PubNub channel or their presence state changes, by polling the channel's Here Now occupant list.
Action
Get channel metadataGet App Context metadata for a channel.
Action
Get Channel PresenceGets current occupancy and user list for a PubNub channel.
Action
Get user metadataGet App Context metadata for a user.
Action
List channelsList all channels with App Context metadata.
Action
List usersList all users with App Context metadata.
Action
Publish MessagePublishes a message to a PubNub channel.
Action
Send signalSend a lightweight signal to a channel.
Action
Update channel metadataSet/update App Context metadata for a channel.
Action
Update user metadataSet/update App Context metadata for a user.
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 HelloSign
HelloSign to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
HelloSign to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
HelloSign to MailchimpMailchimp marketing automation and email platform.
HelloSign to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
HelloSign to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
HelloSign to JIRAAtlassian JIRA Cloud — issue tracking and project management.
More into PubNub
HubSpot to PubNubHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PubNubGoogle Sheets
Gmail to PubNubGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PubNubGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PubNubGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PubNubMailchimp marketing automation and email platform.
Questions
HelloSign and PubNub, answered
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 PubNub when something happens in HelloSign?
Any of PubNub's 9 actions, including Send signal, Update channel metadata, Update user metadata and Get channel metadata. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PubNub to HelloSign?
Yes. When something happens in PubNub, your agent can act in HelloSign too. This page covers both directions: PubNub's triggers and HelloSign's actions are listed here as well.
Do I have to build a connector for HelloSign or PubNub?
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.