Skip to content
MaskioEU

Make

Make can keep the scenario. The model module should not see the lead.

Add an HTTP module to the chat proxy before the model, or point an MCP-capable agent at the gateway. Make’s execution history is still Make’s. Store the tokenized body if you must store anything.

A concrete scenario

A webhook receives a form with a name, email, and IBAN. The next module posts that JSON to Maskio. The OpenAI module receives [PERSON_1] and [IBAN_1]. A later CRM module writes the original values only if your scenario still has them in a Make variable that never went to the model. Better: let the gateway restore on the MCP write, so Make itself does not reassemble the raw record.

Questions

Will this scrub Make’s existing history?+

No. It changes what future runs send to the model. Delete old history in Make if it already contains personal data.

Which plan?+

The proxy is on every plan, including Free, inside the monthly page quota.

See it on a payload you control.

The sandbox and the free tools run before you create an account.