Profanity Filter API + Intercom

Send the response straight into Intercom — connected through Zapier, Make, or n8n, no code required.

WhenIntercomNew conversation
trigger
RunProfanity Filter APIReturns the response
action
ThenIntercomCreate user

The Profanity Filter API in Intercom.

Intercom connects businesses with customers through messaging. Integrating APIs with Intercom enables intelligent lead qualification, automated data enrichment, and context-aware conversations. Give your team the data they need instantly.

Workflows worth wiring.

Validate visitor email addresses before starting conversations
Enrich lead profiles with company data from business APIs
Score conversations based on external data signals
Automatically tag users based on their domain or company type

Ready-made ideas.

New conversation started Filter profanity → tag conversation

Screen new conversation messages

When a new Intercom conversation starts, check the message for profanity and tag the conversation as flagged if isProfane is true.

New message received Filter profanity → add note if profane

Moderate user messages in real-time

Run the profanity filter on incoming Intercom messages and add an internal note with the profaneWords count when content is flagged.

Connect it in a few steps.

Set up with Zapier
  1. 1
    Set the trigger. Create a Zap with Intercom as the trigger app and "New conversation" as the event. Connect your account.
  2. 2
    Add the API action. Add APIVerve as the action, select the Profanity Filter API, and map your trigger data to the request.
  3. 3
    Send it back. Add a second Intercom action for "Create user" and map the returned fields (like isProfane) into it.
  4. 4
    Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.
Set up with Make
  1. 1
    Add the trigger. Create a scenario and add a Intercom module set to "New conversation". Authenticate your account.
  2. 2
    Call the API. Add an HTTP module pointing at api.apiverve.com/v1/profanityfilter with your x-api-key header. Pass the trigger's data as the input.
  3. 3
    Parse & map. Add a JSON module to read the response, then a Intercom module for "Create user". Map fields like data.isProfane into place.
  4. 4
    Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.
Set up with n8n
  1. 1
    Add the trigger node. Start a workflow with a Intercom trigger node for "New conversation" and connect your credentials.
  2. 2
    Add an HTTP Request node. Point it at api.apiverve.com/v1/profanityfilter using Header Auth (x-api-key). Feed in the trigger data.
  3. 3
    Map with expressions. Add a Intercom node for "Create user" and reference the response with expressions such as {{ $json.data.isProfane }}.
  4. 4
    Execute & activate. Execute manually to verify, then activate the workflow for production.

What Intercom receives.

isProfanetrue
filteredText"Today is so **** hot! Why the **** would anyone go outside?"
mask"*"
trimmedfalse
profaneWords2

Intercom + Profanity Filter API FAQ

How do I enrich Intercom users with external data?
Trigger on new users or conversations, extract identifiers like email or company domain, call enrichment APIs, and update Intercom user attributes.
Can I validate emails in Intercom before agents respond?
Yes. Set up automations that validate new user emails and add tags or notes indicating validity. Agents can see this information before engaging.
How do I prioritize Intercom conversations with API data?
Enrich users with external data (company size, plan value, etc.) and use Intercom's rules to prioritize based on these custom attributes.

Connect the Profanity Filter API to Intercom. One key, no code, live in minutes.

Scaling up?

Volume pricing, custom SLAs, and dedicated support for high-traffic teams.

Contact sales