MoonClerk is an easy-to-use payment form builder for Stripe.
Moonclerk currently provides 5 triggers that can start a workflow and 2 actions a workflow can run. Use those building blocks to connect customer and order activity to the relationship record behind it.
New Payment
Triggers when a payment is created in any state (failed, succeeded, etc).
New Plan
Triggers when a new plan is created in MoonClerk
Payment Succeeds
Plan Ended
Triggers when a plan is canceled or when the set number periods have been exhausted.
Plan Payment Failed
Triggers when a payment related to a plan has failed.
Retrieve Plan
Retrieve a customer plan from MoonClerk using the customer ID
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Moonclerk event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Payment
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Moonclerk action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Retrieve Plan
Combine Moonclerk with another integration and Coherence records to connect customer and order activity to the relationship record behind it.
Starts with
New Payment
Finishes with
Retrieve Plan, then preserve the outcome in Coherence
The exact authentication fields depend on Moonclerk. The workflow structure stays straightforward:
Authorize the Moonclerk account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Moonclerk or provide a complementary trigger or action.
Moonclerk currently provides 5 triggers that can start a workflow and 2 actions a workflow can run. Use those building blocks to connect customer and order activity to the relationship record behind it.
Moonclerk currently lists 5 triggers and 2 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Moonclerk triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
