Profanity Filter API + Notion Integration

Why connect them

The Profanity Filter API in Notion.

Notion is the all-in-one workspace for notes, docs, and databases. Connecting APIs to Notion enables automated documentation, dynamic databases, and self-updating knowledge bases. Build living documents that stay current without manual updates.

What you can build

Workflows worth wiring.

Automatically create documentation pages when new API endpoints are deployed

Build a competitor tracking database that updates with the latest company data

Create a reading list that enriches book entries with metadata from external APIs

Maintain an always-current list of domain registrations with expiry dates

Templates

Ready-made ideas.

New database item created Filter profanity → update status property

Screen wiki entries for profanity

When a new entry is added to your Notion database, run the profanity filter and set a status property based on the isProfane result.

New database item created Filter profanity → save filteredText property

Store filtered versions of content

Automatically filter new Notion entries and store the filteredText as a property alongside the original content.

Setup

Connect it in a few steps.

Set up with Zapier

1
Set the trigger. Create a Zap with Notion as the trigger app and "New database item" as the event. Connect your account.
2
Add the API action. Add APIVerve as the action, select the Profanity Filter API, and map your trigger data to the request.
3
Send it back. Add a second Notion action for "Create page" and map the returned fields (like isProfane) into it.
4
Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.

Set up with Make

1
Add the trigger. Create a scenario and add a Notion module set to "New database item". Authenticate your account.
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
Parse & map. Add a JSON module to read the response, then a Notion module for "Create page". Map fields like data.isProfane into place.
4
Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.

Set up with n8n

1
Add the trigger node. Start a workflow with a Notion trigger node for "New database item" and connect your credentials.
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
Map with expressions. Add a Notion node for "Create page" and reference the response with expressions such as {{ $json.data.isProfane }}.
4
Execute & activate. Execute manually to verify, then activate the workflow for production.

The payload

What Notion receives.

isProfanetrue

filteredText"Today is so **** hot! Why the **** would anyone go outside?"

mask"*"

trimmedfalse

profaneWords2

Profanity Filter API + Notion