Webhooks: Connect Nviti.ng to Your External Tools

Webhooks let Nviti.ng send real-time data to external services like n8n and ActivePieces whenever specific events happen. Instead of polling for data, your automation tools can receive an instant push notification — triggering workflows, updating systems, or sending alerts automatically.

What Are Webhooks?

A webhook is an HTTP request that Nviti.ng sends to a URL you specify when something happens. It's like a reverse API — instead of your tool asking Nviti.ng for data, Nviti.ng tells your tool the moment something occurs.

Common use cases:

• Trigger an n8n workflow when a new visitor submits a form
• Notify ActivePieces when a workflow completes or fails
• Sync data between Nviti.ng and your CRM or database
• Send real-time alerts to Slack or email when specific events fire

Accessing Webhooks

1. Open your Workspace
2. Go to Monitoring in the sidebar
3. Click Webhooks

Creating a Webhook

1. Click Create at the top of the Webhooks page
2. Fill in the fields:

Webhook Name

A friendly label to identify this webhook (e.g., "n8n New Lead Flow" or "ActivePieces Order Alert"). This name is shown in your webhook list and logs.

Webhook URL (required)

The production URL that Nviti.ng will send POST requests to. This must be a publicly accessible HTTPS endpoint.

Test Webhook URL (optional)

A separate URL to use during testing. If left blank, Nviti.ng will append /test to the production URL (e.g., https://your-site.com/webhook/test).

Bearer Token (optional)

If your endpoint requires authentication, you can provide a bearer token. This will be sent as the Authorization: Bearer <token> header with every request.

Active Toggle

Turn the webhook on or off without deleting it. Inactive webhooks won't send any requests.

Sending a Test Webhook

Before going live, test your webhook to make sure it receives payloads correctly:

1. Open your webhook record
2. Scroll to the Test Webhook section
3. Review or edit the Test Payload (JSON) — this is what will be sent
4. Click Send Test Webhook
5. Check the Response panel to see the HTTP status and response body

The test payload includes:

{
  "test": true,
  "trigger": "manual_test",
  "timestamp": "<current ISO 8601 time>",
  "message": "This is a test webhook trigger",
  "user": {
    "id": "123",
    "name": "Test User"
  }
}

You can also send a quick test from the Webhooks list page by clicking Test on any webhook row.

Webhook Table

Payload Format

When a webhook fires, it sends a POST request with:

• Content-Type: application/json
• Body: Event-specific JSON payload
• Headers:
  • Authorization: Bearer <your_token> (if configured)
  • X-Nviti-Event: <event_type> — the name of the event that triggered this webhook
  • X-Nviti-Delivery: <uuid> — a unique ID for this delivery attempt

Viewing Webhook Runs

Each webhook has a Runs relation manager that logs every delivery attempt — both successful and failed. Use this to debug issues and verify that your integrations are working correctly.

Managing Bearer Tokens

• Bearer tokens are stored securely and masked in the UI (shown as ••••••••)
• Tokens are only updated when a new value is provided — leaving the field blank preserves the current token
• If you need to rotate a token, simply save a new value in the webhook form

Best Practices

• Always test before enabling — Use the test webhook feature to verify your endpoint works before going live
• Use separate test URLs — Configure a staging/test endpoint to avoid triggering production workflows during development
• Monitor your runs log — Check the Runs section regularly to catch failed deliveries early
• Secure your endpoints — Use the bearer token option to ensure only Nviti.ng can trigger your webhooks
• Keep URLs accessible — Your webhook URL must be publicly reachable over HTTPS

Troubleshooting

Webhook Test Fails

• Verify the URL is correct and publicly accessible
• Make sure your server accepts POST requests with a JSON body
• Check your server's firewall or authentication rules

Production Webhooks Not Firing

• Confirm the webhook is set to Active
• Check the Runs log for failed delivery attempts
• Verify the trigger event is actually occurring in your workspace

Receiving No Response

• Ensure your endpoint returns a 2xx HTTP status within a reasonable timeout
• Nviti.ng may retry failed deliveries — make sure your endpoint is idempotent

Keywords

webhooks, n8n integration, ActivePieces integration, HTTP callbacks, automation triggers, real-time notifications, external integrations, webhook testing, webhook security, API integration, workflow automation