--- title: "Connect HelloSign to Google Cloud Scheduler - APIANT.ai" description: "When \"New Signature Request\" fires in HelloSign, your agent runs \"Create HTTP Job\" in Google Cloud Scheduler." canonical: "https://apiant.ai/connect/hellosign-to-google-cloud-scheduler" --- # Connect HelloSign to Google Cloud Scheduler When **New Signature Request** fires in [HelloSign](https://apiant.ai/connections/hellosign), your agent runs **Create HTTP Job** in [Google Cloud Scheduler](https://apiant.ai/connections/google-cloud-scheduler). Describe the whole flow and it is built, tested on every scenario and kept running. HelloSign **1** trigger HelloSign **8** actions Google Cloud Scheduler **8** 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 Google Cloud Scheduler 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 HelloSign can start in Google Cloud Scheduler - When **New Signature Request** in HelloSign then **Create HTTP Job** in Google Cloud Scheduler - When **New Signature Request** in HelloSign then **Update Job** in Google Cloud Scheduler 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 Google Cloud Scheduler ## Triggers and actions 1 trigger · 16 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. - Action **Create HTTP Job** Creates a Cloud Scheduler job that calls an HTTP URL on a cron schedule. - Action **Delete Job** Permanently deletes a Cloud Scheduler job. - Action **Get Job** Returns a Cloud Scheduler job's schedule, target and current state. - Action **List Jobs** Returns the Cloud Scheduler jobs in a project location. - Action **Pause Job** Pauses a Cloud Scheduler job so it stops running on its schedule until resumed. - Action **Resume Job** Resumes a paused Cloud Scheduler job so it runs on its schedule again. - Action **Run Job Now** Runs a Cloud Scheduler job immediately. The job must be enabled; a paused job has to be resumed first. - Action **Update Job** Changes a Cloud Scheduler HTTP job's schedule, time zone, URL, method or description. Fields left blank are not changed. ## Each app on its own - [ **HelloSign** Dropbox Sign (formerly HelloSign) e-signature platform.](https://apiant.ai/connections/hellosign) - [ **Google Cloud Scheduler** Managed cron service for scheduling HTTP, Pub/Sub and App Engine jobs on Google Cloud.](https://apiant.ai/connections/google-cloud-scheduler) 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 Google Cloud Scheduler - [ **HubSpot to Google Cloud Scheduler** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-google-cloud-scheduler) - [ **Salesforce to Google Cloud Scheduler** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-google-cloud-scheduler) - [ **Slack to Google Cloud Scheduler** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-google-cloud-scheduler) - [ **Google Sheets to Google Cloud Scheduler** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-google-cloud-scheduler) - [ **Gmail to Google Cloud Scheduler** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-google-cloud-scheduler) - [ **Google Calendar to Google Cloud Scheduler** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-google-cloud-scheduler) Questions ## HelloSign and Google Cloud Scheduler, 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 Google Cloud Scheduler when something happens in HelloSign? Any of Google Cloud Scheduler's 8 actions, including Create HTTP Job, Update Job, Get Job and List Jobs. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Google Cloud Scheduler to HelloSign? Google Cloud Scheduler has no triggers in the catalog today, so automations start in HelloSign. If you need the other direction, ask: your agent reads Google Cloud Scheduler's API documentation and adds it. ### ### Do I have to build a connector for HelloSign or Google Cloud Scheduler? 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 Google Cloud Scheduler 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.