Integration
Connect Google Tasks to Mercury
When New Task Created fires in Google Tasks, your agent runs Add customer in Mercury. 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 Google Tasks and Mercury to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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 Google Tasks can start in Mercury
When New Task Created in Google Tasks
then Add customer in Mercury
When New Task List Created in Google Tasks
then Get invoice in Mercury
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 Google Tasks and Mercury
Triggers and actions 5 triggers · 33 actions
Trigger
New Task CreatedTriggers when a new task is created in a Google Tasks list. Uses timestamp filtering (updatedMin) to efficiently detect new tasks.
Trigger
New Task List CreatedTriggers when a new Google Tasks task list is created. This trigger monitors Google Tasks and fires when new task lists are detected.
Trigger
Task Details ChangedTriggers when a specific task's details change. This trigger monitors a single Google Task and fires when any of its details (title, notes, status, due date, completion, position) are modified.
Trigger
Task List ChangedTriggers when a task list changes (title or content updates). This trigger monitors a specific Google Tasks list and fires when changes are detected.
Trigger
Task UpdatedTriggers when an existing task is updated in a Google Tasks list. This trigger monitors a specific task list and fires when tasks are modified.
Action
Batch ExecuteExecutes multiple Google Tasks API operations in a single HTTP batch request and returns structured per-item results. Use this to reduce LLM tool invocations when performing bulk operations like updating many tasks, moving tasks, or deleting multiple items. Note: Each sub-request still counts toward API quota; batching primarily reduces HTTP overhead and tool call count.
Action
Clear TasksPermanently clears all completed tasks from a specified google tasks list; this action is destructive and idempotent.
Action
Create Task ListCreates a new task list with the specified title.
Action
Delete TaskDeletes a specified task from a given task list in google tasks.
Action
Delete Task ListPermanently deletes an existing google task list, identified by `tasklist id`, along with all its tasks; this operation is irreversible.
Action
Get TaskUse to retrieve a specific google task if its `task id` and parent `tasklist id` are known.
Action
Get Task ListRetrieves a specific task list from the user's google tasks if the `tasklist id` exists for the authenticated user.
Action
Insert TaskCreates a new task in a given `tasklist id`, optionally as a subtask of an existing `task parent` or positioned after an existing `task previous` sibling, where both `task parent` and `task previous` must belong to the same `tasklist id` if specified.
Action
List Task ListsFetches the authenticated user's task lists from google tasks; results may be paginated.
Action
List TasksRetrieves tasks from a google tasks list; all date/time strings must be rfc3339 utc, and `showcompleted` must be true if `completedmin` or `completedmax` are specified.
Action
Move TaskMoves the specified task to another position in the destination task list.
Action
Patch TaskPartially updates an existing task (identified by `task id`) within a specific google task list (identified by `tasklist id`), modifying only the provided attributes from `taskinput` (e.g., `title`, `notes`, `due` date, `status`) and requiring both the task and list to exist.
Action
Patch Task ListUpdates the title of an existing google tasks task list.
Action
Update TaskUpdates the specified task.
Action
Update Task FullTool to fully replace an existing Google Task using PUT method. Use when you need to update the entire task resource, not just specific fields. This method requires all required fields (id, title) and replaces the complete task, unlike PATCH which supports partial updates.
Action
Update Task ListUpdates the authenticated user's specified task list.
Action
Add customerCreates a new Accounts Receivable customer in Mercury that you can invoice.
Action
Add internal transferTransfers funds between two Mercury accounts in the same organization and returns the paired debit and credit transactions.
Action
Add recipientCreates a new payment recipient in Mercury, with optional ACH, wire, real-time payment or check details.
Action
Get invoiceReturns the details of a Mercury invoice, including its customer, amount, status, dates and line items.
Action
Get organizationReturns your Mercury organization's details, including legal business name, EIN, DBAs and subscription tier.
Action
Get recipientReturns the details of a Mercury payment recipient, including name, emails, default payment method and routing information.
Action
Get transactionReturns a single Mercury transaction by its ID, including amount, status, counterparty, attachments and related transactions.
Action
List accountsReturns all Mercury bank accounts in your organization, including balances, account and routing numbers, and status.
Action
List account statementsReturns the monthly statements for a Mercury checking or savings account, optionally limited to a date range.
Action
List categoriesReturns the organization's custom expense categories used to classify transactions.
Action
List customersReturns the accounts receivable customers on your Mercury account (up to 1000).
Action
List invoicesReturns the accounts receivable invoices in your Mercury organization, up to 1,000 at a time.
Action
List recipientsReturns the payment recipients saved in your Mercury account (up to 1000).
Action
List transactionsReturns transactions across all Mercury accounts, optionally filtered by date, status, account, card, category or search text.
Action
Send moneySends money from a Mercury account to a saved recipient by ACH, check, domestic wire or real-time payment. Returns the created transaction.
Action
Update recipientUpdates an existing payment recipient's name, contact details and payment routing information.
Action
Update transactionUpdates the note and/or category of an existing Mercury transaction.
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 Google Tasks
Google Tasks to BigMLBigML is a machine learning platform for building, evaluating, and running predictive models.
Google Tasks to GristGrist combines the flexibility of a spreadsheet with the robustness of a database to organize your data...
Google Tasks to Mistral AIMistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...
Google Tasks to MorgenMorgen is an all-in-one app for your time management
Google Tasks to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Google Tasks to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
More into Mercury
HubSpot to MercuryHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to MercurySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to MercurySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to MercuryGoogle Sheets
Gmail to MercuryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to MercuryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Google Tasks and Mercury, answered
What can start an automation from Google Tasks?
Any of Google Tasks's 5 triggers in the catalog, including New Task Created, New Task List Created, Task Details Changed and Task List Changed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mercury when something happens in Google Tasks?
Any of Mercury's 17 actions, including Send money, Update recipient, Update transaction and Add customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mercury to Google Tasks?
Mercury has no triggers in the catalog today, so automations start in Google Tasks. If you need the other direction, ask: your agent reads Mercury's API documentation and adds it.
Do I have to build a connector for Google Tasks or Mercury?
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 Google Tasks and Mercury 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.