Background
Many no-code users want to validate PEC addresses as part of onboarding flows in Make (formerly Integromat) or Zapier, but Openapi is not yet listed as an official app on those platforms.
n8n offers more flexibility — you can define custom HTTP auth and build reusable workflow templates. This issue explores what a self-hosted n8n + Openapi integration could look like for PEC validation.
Proposed flow
New lead in CRM → n8n trigger → Openapi PEC check → branch:
├── valid PEC → tag lead as "pec-verified" → send welcome email
└── invalid PEC → tag lead as "pec-invalid" → send correction request
PHP proxy endpoint
$client = new Client($token);
$result = json_decode($client->get('https://pec.openapi.com/check', [
'pec' => $_GET['pec']
]), true);
http_response_code($result['valid'] ? 200 : 422);
echo json_encode($result);
Open questions
- Is there an official Openapi app coming to Make or Zapier?
- Would a collection of n8n workflow JSON templates be a good addition to the
examples/ folder?
- How should we handle PEC addresses that are syntactically valid but unreachable (DNS/SMTP checks)?
Background
Many no-code users want to validate PEC addresses as part of onboarding flows in Make (formerly Integromat) or Zapier, but Openapi is not yet listed as an official app on those platforms.
n8n offers more flexibility — you can define custom HTTP auth and build reusable workflow templates. This issue explores what a self-hosted n8n + Openapi integration could look like for PEC validation.
Proposed flow
PHP proxy endpoint
Open questions
examples/folder?