ProofTell integrations

The connectors that put ProofTell's checks inside the platforms teams already use. Each one runs on its platform and takes a ProofTell API key (pt_live_…, or pt_test_… for the free sandbox); nothing of a customer's is stored here or by us. HubSpot and GoHighLevel are the exception (D190): OAuth apps whose backend is ProofTell's api, which keeps each connected account's tokens, encrypted (D192). The four actions are the same everywhere — look up a phone number, verify an email address, look up an IP address, assess the risk of an identity — on the public API (https://prooftell.com/docs). How each is published, re-published and reviewed: the workspace's RUNBOOK.md → Integrations; why: DECISIONS.md D188.

Folder	What	Where it goes
zapier/	The Zapier integration (zapier-platform-cli)	Zapier's app directory
n8n-nodes-prooftell/	The n8n community node, an npm package	npm, then n8n's verified community nodes
make/	The Make custom app, as files	Make's integrations page (a community app)
power-platform/	The Power Platform independent-publisher connector	microsoft/PowerPlatformConnectors by PR
node-red/	The Node-RED node, an npm package	npm, then Node-RED's Flow Library
mcp/	The MCP server, an npm package (stdio)	npm, then the official MCP Registry
activepieces/	The Activepieces piece	activepieces/activepieces by PR
windmill/	The Windmill resource type and scripts	Windmill's Hub
postman/	The Postman collection, generated from the api's OpenAPI	Postman's API Network
hubspot/	The HubSpot app, two developer projects (production, staging) generated from one definition: OAuth and four workflow actions on ProofTell's own backend	HubSpot's marketplace