MoonClerk is a platform that enables businesses to accept recurring and one-time online payments.
MoonClerk is a platform that enables businesses to accept recurring and one-time online payments. On Nagent, Moonclerk is exposed as a fully-configurable payment processing integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Moonclerk into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Moonclerk to automate the kinds of tasks payment processing teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Moonclerk into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Moonclerk, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MOONCLERK_LIST_CUSTOMERSTool to list customers (plans) from MoonClerk. Use when you need to retrieve customer data with optional filters. Use after authenticating API credentials.
Input parameters
Filter by subscription status.
The associated MoonClerk form ID to filter customers.
Customers created on or before this date (YYYY-MM-DD).
Customers created on or after this date (YYYY-MM-DD).
Subscriptions due to bill on or before this date (YYYY-MM-DD).
Subscriptions due to bill on or after this date (YYYY-MM-DD).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MOONCLERK_LIST_DISCOUNTSTool to retrieve a list of all discounts applied to customers. Use after authenticating API credentials.
Input parameters
Filter by subscription status.
Filter discounts by associated MoonClerk form ID.
Filter customers created on or before this date (YYYY-MM-DD).
Filter customers created on or after this date (YYYY-MM-DD).
Filter subscriptions due to bill on or before this date (YYYY-MM-DD).
Filter subscriptions due to bill on or after this date (YYYY-MM-DD).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MOONCLERK_LIST_FORMSTool to retrieve a list of all payment forms. Use after authenticating to inspect available payment forms.
Input parameters
Page number to retrieve, starting at 1
Number of forms per page
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MOONCLERK_LIST_PAYMENTSTool to list payments. Use when you need to retrieve all payments or filter by form, customer, date range, or status after authenticating.
Input parameters
Filter payments by status. Valid values: successful, refunded, failed
Include payments charged on or before this date (YYYY-MM-DD)
MoonClerk form ID to filter payments (e.g., 5346)
Include payments charged on or after this date (YYYY-MM-DD)
MoonClerk customer ID to filter payments (e.g., 12742)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MOONCLERK_LIST_SUBSCRIPTIONSTool to list subscriptions. Use when you need to retrieve all subscriptions after authenticating.
Input parameters
Filter subscriptions by status. Valid options: active, canceled, expired, past_due, pending, unpaid
Filter subscriptions by the associated MoonClerk form ID (e.g., 5346)
Include subscriptions due to bill on or before this date (YYYY-MM-DD)
Include subscriptions due to bill on or after this date (YYYY-MM-DD)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 60 agents privately built on Nagent that already use Moonclerk.
Build on Nagent
Connect Moonclerk to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Moonclerk, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Moonclerk is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Moonclerk is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Moonclerk steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Moonclerk event fires, the agent kicks off automatically.
Every Moonclerk action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Moonclerk ships with 5 pre-built payment processing actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Moonclerk together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Moonclerk-based workflows tailored to your business.