Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Moonclerk

MoonClerk is an easy-to-use payment form builder for Stripe.

CategoryCommerce
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Moonclerk with Flows360

MoonClerk is an easy-to-use payment form builder for Stripe.

Use the Moonclerk connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and 5 triggers.

Available actions

  • Retrieve Plan
  • Custom API Call

Available triggers

  • New Payment
  • New Plan
  • Payment Succeeds
  • Plan Ended
  • Plan Payment Failed

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Moonclerk
  • Package: @activepieces/piece-moonclerk@0.1.0
  • Exact artifact digest: sha256:6c239f66fc13494f04ddc287c8d51c48526bc127ad69c715cb82ee1e972d14a6
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Retrieve Plan (retrivePlan), Retrieve a customer plan from MoonClerk using the customer ID Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Payment, webhook.
  • New Plan, webhook.
  • Payment Succeeds, webhook.
  • Plan Ended, webhook.
  • Plan Payment Failed, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions2
Triggers5

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Retrieve Plan Yes No Retrieve a customer plan from MoonClerk using the customer ID
Custom API Call Yes No Make a custom API call to a specific endpoint
New Payment Yes No webhook trigger declared by the pinned package.
New Plan Yes No webhook trigger declared by the pinned package.
Payment Succeeds Yes No webhook trigger declared by the pinned package.
Plan Ended Yes No webhook trigger declared by the pinned package.
Plan Payment Failed Yes No webhook trigger declared by the pinned package.

Supported actions

Retrieve Plan · Read

Retrieve a customer plan from MoonClerk using the customer ID

retrive_plan · Risk: low · Retry: safe

Inputs

  • customerId · string · Required, The ID of the customer to retrieve the plan for
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Payment · Webhook

Triggers when a payment is created in any state (failed, succeeded, etc).

Inputs

  • markdown · string
New Plan · Webhook

Triggers when a new plan is created in MoonClerk

Inputs

  • markdown · string
Payment Succeeds · Webhook

Inputs

  • markdown · string
Plan Ended · Webhook

Triggers when a plan is canceled or when the set number periods have been exhausted.

Inputs

  • markdown · string
Plan Payment Failed · Webhook

Triggers when a payment related to a plan has failed.

Inputs

  • markdown · string

Setup

Setup

  1. Add the Moonclerk connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-moonclerk@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Moonclerk connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-moonclerk@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com