makeNexis with Make
Nexis finds names, emails, card numbers, health and ID numbers in your text, then redacts, masks or replaces them before the text reaches an AI model, your CRM or a third party. Detection follows the regulation you choose.
Works today through Make's HTTP module. Native Make app coming soon.
Clean the text before it moves on
Add one HTTP module before any step that sends text outside your scenario. Later modules map the cleaned text instead of the original.
HTTP: Make a requestReplaces each value with its type.
Pick a regulation
Choose a country and regulation, such as UK GDPR or HIPAA. Nexis looks for the personal data that regulation covers.
Choose what happens to it
Redact, replace with the type, mask, hash, tokenize or swap in realistic fake values. Encryption is also available through the API.
Route on the result
Map anonymised_text into your next module. Add a Make filter on pii_entity_count to send anything with personal data to a review step.
Regulations and jurisdictions supported
Your plan sets how many regulations you can use.
UK GDPR
United Kingdom
HIPAA
United States
Privacy Act
Australia
Privacy Act
New Zealand
GDPR
Germany
English and German textPIPEDA
Canada
How to get started
Get your free API key
Sign up for Nexis with your work email. Then create a key in the dashboard under API Integration.
Add the HTTP module
In your scenario, add HTTP > Make a request after your trigger. Set the method to
POSTand the URL tohttps://api.nexis.intelation.com/api/text/.Add your key and the body
Add a header named
Authorizationwith the valueBearer YOUR_API_KEY. Set the body type to Raw, content type to JSON, and paste the request below.Use the result
Set Parse response to Yes and run the module once. Then map
anonymised_textandpii_entity_countinto your next modules.
The request body
{
"text": "{{1.message}}",
"regulation": "UK GDPR",
"country": "United Kingdom",
"language": "en",
"anonymisation_method": "redact"
}Replace {{1.message}} with the text you map from your trigger, and use a regulation and country included in your plan. If your text can contain quotes or line breaks, build this body with the JSON > Create JSON module first, so the request stays valid.
Fine-tune what Nexis looks for
Add any of these to the body:
allow_list: values to keepdeny_list: values to always hide, like a project code nameselected_entitiesorexcluded_entities: only process some types of personal data, or all except some
All fields are in the API documentation.
Questions
Can't find your answer? Talk to us.
Is there a native Nexis app for Make?
Does Nexis store my text?
Will it catch every piece of personal data?
pii_entity_count in your scenario, add values you always want hidden to deny_list, and review high-risk flows.Can I get the original data back?
encryption as the method with your own encryption_key, then call /api/decrypt/ with the same key. The other methods are one-way. See the API documentation.