Please expand Moxie’s public API and Pabbly integration to support programmatic creation and management of forms. Required capabilities: Create a form from scratch Create a form from an existing template Retrieve and search forms Add, update, reorder and remove form fields Configure field types, labels, instructions, placeholders and validation Mark fields as required or optional Configure conditional field visibility and branching logic Map fields to Moxie client, contact, opportunity and ticket properties Configure whether a submission creates a lead, updates a contact or creates a ticket Associate forms with clients, opportunities, agreements or projects Set confirmation messages and redirect URLs Publish, unpublish, duplicate and archive forms Retrieve the public form and embed URLs Receive submission webhooks containing the form ID, submission ID and related Moxie object IDs The API should support idempotency keys and external IDs so an automation can safely create or update a form without producing duplicates. Updating a form should not remove existing fields or submissions unless deletion is explicitly requested. This would allow agencies to generate standardized onboarding, discovery, access-request and support forms automatically when a client signs an agreement or begins a new service. For example, Pabbly could select the appropriate form template, customize it for the engagement, map it to the correct client and include its link in the onboarding workflow. Ideally, the native Pabbly integration would include corresponding actions such as: Create Form Create Form from Template Find Form Update Form Add or Update Form Field Publish Form Retrieve Form Link Form Submitted trigger
