Marketing · Forms
The response arrives. Even when the destination refuses.
A form on your site, with one line, or on a ready-made link. Each response becomes a signed event for the destinations you choose, with the page and campaign it came from, and it waits in the queue until the destination accepts it.
Same login for every dashboard in the line. A code arrives in your email; you paste it once. The dashboard is in Portuguese for now.
Why this exists
A lost response leaves no
TRACE.
The form says thank you, the webhook fails in the middle of the night and nobody finds out. Here every delivery is written to an outbox before it goes out, and a response the destination refused waits in the queue, with the reason in plain sight.
- The secret changed at the destination that broke the deliveries
- The bot that filled the spreadsheet, or the captcha that drove people away
- The response nobody knows which page it came from
The whole path
Build, install, filter, deliver.
And the response is not lost on the way.
1 · Build
Seven field types, up to 40 per form, and an email field to publish.
Each field has a label, a required setting and help text. To publish, the form needs an email field: without it, the response does not identify the person. Each change to a published form creates the next version.
fields Short text · Email · Phone (WhatsApp)
Single choice · Multiple choice
Long text · Hidden
status Draft · Published · Paused
publish requires an email field
version each published change is the next version2 · Install
One line on your site, or a ready-made link.
The script draws a component with Shadow DOM, with no dependencies. It inherits the font and text color of the page and does not break your CSS. Without a site, the ready-made link opens the form on its own. If you want, limit it to up to 20 domains where it runs.
<script src="https://forms.worker.mymarketing.click/embed.js" data-form="<form code>" defer></script> <!-- or, with the script already on the page --> <forms-embed form="<form code>"></forms-embed> or the ready-made link https://forms.worker.mymarketing.click/f/<code>
3 · Against bots
No captcha. And what gets blocked is visible.
A hidden honeypot field, a minimum time checked by the server and a limit per address. Whoever was blocked sees the same success screen, so the bot does not learn. In the dashboard, each block shows the reason and can become a response.
honeypot a hidden field only a bot fills in
time under 3 s to submit: blocked
limit 5 per hour, per address, per form
blocked counted, with the reason, and visible
"Aceitar como resposta" (Accept as response),
if it was a person4 · Origin
Each response knows the page, campaign and link it came from.
Hidden fields fill themselves from the page address: the source, the campaign and the short link that brought the person. The response also stores the page and the form version the person saw.
page /trial-class utm_source instagram utm_campaign november-class lk clay-2 version 3, the one the person saw
5 · Deliver
The response goes out signed. If the destination refuses, it waits.
Each response becomes a signed event in the Standard Webhooks format, sent to the destinations you choose: your CRM, a spreadsheet, an automation. Every delivery is written to an outbox before it goes out, and nothing is discarded when the destination fails.
form.viewed form.submitted form.consented
form.blocked form.delivery_failed
failed retried after 1 min, 5 min, 30 min,
2 h and 12 h; then resend by hand
401 · 403 held, without using a retry
signed: Standard Webhooks, x-ccm headersModel Context Protocol
The agent fills in. Only the person consents.
Four tools do everything the dashboard does, through the same API: the agent reads the guide, reads, creates, edits, publishes and generates or rotates the key. It creates, changes and publishes the form, and submits a response like a visitor. The whole catalog costs the agent fewer than 3,400 characters before the first word.
The server's limits
- Consent never. An agent response with consent is refused.
- Delete, revoke or cancel only after your yes, in the conversation: the first call only asks and shows what will happen.
- Submit responses at most 5 per hour on each form.
The account comes from the token and never from an argument. The agent submits at most 5 responses per hour on each form.
The yardstick
What It Does, and Where It Stops
The limits, stated before you need to ask.
Field types
Seven
Short text, email, phone, single choice, multiple choice, long text and hidden. No conditional logic and no file upload.
Captcha
None
Honeypot, a minimum time of 3 s and a limit of 5 per hour per address. Blocked attempts stay in the dashboard for 30 days.
IP of the respondent
Never in plain text
Stored as a hash, with only the start of the address kept for display.
Where it goes
The destinations you choose
Signed webhook, to up to 20 addresses. Only responses come in: Forms does not receive events from other systems.
Confirmation email
Through Messages
With the Messages key of your account, at most one per address, per form, every 24 hours. Your own SMTP does not send yet.
Agent
Submits, never consents
Through the MCP server, with four tools that do what the dashboard does. Deleting a response asks for your yes, in the conversation.
Pricing
1, 3, 9 or 99 forms
Free to start
1 form, with all responses.
What changes between plans is how many forms the account keeps. Responses, destinations and MCP are in all of them, with no plan limit. Prices are in Brazilian reais (BRL), charged by Stripe. No card, and the free plan never expires. The yearly plan costs ten months.
FAQ
The Questions, in the Order They Come Up
Does your form need something that is not here?
Talk directly to the person who wrote the code. A real case changes the design.
Marketing · Forms
The response arrives. Even when the destination refuses.
One line on your site, protection against bots without captcha, and every response delivered signed.