Webhook

Webhook + Konnectify

Webhook Integration with Konnectify

Make HTTP requests to any webhook endpoint with flexible authentication, custom headers, and payload options—ideal for connecting APIs, posting events, and orchestrating cross-app automations.

HTTP Requests 0 Triggers 5 Actions

ON THIS PAGE

→ What is Webhook? → API & authentication → How to connect → Triggers (0) → Actions (5) → Popular automations → FAQ

What is Webhook?

“Webhook” in Konnectify is a universal HTTP connector that lets you call any public (or privately accessible) endpoint using standard HTTP methods. It’s a great fit when an app doesn’t have a native integration, when you need to hit a custom API route, or when you want full control over headers, authentication, and payloads.

By combining Webhook actions with Konnectify workflow logic, you can stitch together APIs, send event notifications, update records in external systems, and build lightweight API-to-API automations without writing code.

New to Webhook?

Use any service that provides an HTTP endpoint (webhooks, REST APIs, internal tools). This connector sends requests to that endpoint from Konnectify.

Learn about webhooks →

Note: This link is informational (not Konnectify-owned).

New to Konnectify?

Build workflows that connect your apps and APIs in minutes using triggers, actions, mapping, and retries.

Create a free account →

What you can automate

•Call external APIs using GET for data retrieval

•Send JSON payloads via POST to create resources

•Update records using PUT for full replacements

•Patch fields using PATCH for partial updates

•Remove resources using DELETE

•Add custom headers (e.g., Content-Type, Authorization, idempotency keys)

API & authentication

Authentication type: Credentials

This connector supports credential-based authentication settings when making requests (for example, adding an API key or token as a header, using Basic Auth, or passing credentials through custom headers). The exact method depends on the endpoint you’re calling.

Common auth patterns to use

Bearer token in header: Authorization: Bearer <token>
API key in header: x-api-key: <key>
Basic Auth (username + password) for legacy endpoints
HMAC signatures (computed in a prior step) passed as headers

API capabilities

Available operations map to standard HTTP methods:

GET — fetch data
POST — create/send data
PUT — replace/update data
PATCH — partial update
DELETE — remove data

Rate limits & plan restrictions

Rate limits and доступ (access) depend on the API you’re calling. If the endpoint enforces quotas, use Konnectify retries, backoff, and batching patterns to avoid request failures.

API docs: refer to the documentation for the specific API you’re calling (e.g., your vendor’s REST API docs). If you’re calling a third-party service, locate their official API reference and confirm required headers, payload schema, and expected response codes.

How to connect

Prerequisites

The destination endpoint URL (including path)
Authentication details required by that endpoint (token / API key / Basic credentials)
Any required headers (Content-Type, Accept, Authorization, etc.)
Payload schema (for POST/PUT/PATCH) and sample test data

Add Webhook to a Workflow

Open your Konnectify Workflow builder.
Click Add step and search for Webhook.
Select the HTTP method action you need (GET/POST/PUT/PATCH/DELETE).

Authorize via Credentials

Choose how your endpoint expects authentication (Bearer token, API key header, Basic Auth, etc.).
Add the required credential value(s) in the action configuration (usually as headers).
If your endpoint requires IP allowlisting, allow Konnectify’s outbound traffic (your network team can help).

Configure the Trigger or Action

Paste the full endpoint URL and set any query parameters.
Add headers such as Content-Type: application/json when sending JSON.
For POST/PUT/PATCH, map your workflow fields into the request body.

Important

Double-check required headers and payload format. Many APIs reject requests due to a missing Content-Type, invalid JSON, or an incorrect auth header.

Test the Workflow

Run a test with a known payload.
Inspect the response status code and body to confirm success.
If the API returns an error (4xx/5xx), update headers/body and retest.

Activate the Workflow

Turn the workflow On.
Monitor initial runs and confirm the destination system receives requests as expected.
Add error handling paths as needed (retries, alerts, or fallback steps).

Triggers 0

This connector doesn’t include native triggers. Use triggers from other apps in your workflow (or a Scheduler trigger) and then use Webhook actions to call your target endpoint.

Actions 5

Use these actions to send requests to any HTTP endpoint. Grouped below by module.

HTTP Requests 5 actions

GET Request

Make an HTTP GET request with authentication and custom headers

POST Request

Make an HTTP POST request with data, authentication and custom headers

PUT Request

Make an HTTP PUT request with data, authentication and custom headers

PATCH Request

Make an HTTP PATCH request with data, authentication and custom headers

DELETE Request

Make an HTTP DELETE request with authentication and custom headers

Popular automations

Examples of common patterns using Webhook actions (paired with triggers from other apps in Konnectify).

Send a notification to a custom webhook when a record changes

When a lead, ticket, or deal updates in another app, call your internal webhook endpoint to notify downstream systems.

App Trigger (e.g., “Updated record”) → POST Request

Fetch enrichment data from an API and update a downstream system

Pull extra details from a third-party API, then pass the response to later steps for mapping and updates.

App Trigger (e.g., “New record”) → GET Request

Sync status updates to a partner system

When an order is fulfilled (or a ticket is resolved), send a partial update to a partner API to keep both systems in sync.

App Trigger (e.g., “Status changed”) → PATCH Request

Clean up external resources on lifecycle events

When a user is deactivated or a subscription ends, remove or deprovision resources in another system using a DELETE call.

App Trigger (e.g., “User removed”) → DELETE Request

FAQ

How does authentication work for the Webhook connector?

Konnectify uses a credentials-based approach: you provide whatever the destination endpoint requires (for example, an API key header, a Bearer token, or Basic Auth). Configure the credentials and headers according to the API’s documentation.

Which plans are supported?

Support depends on the API you’re calling. Many vendors restrict API access to certain paid tiers or require enabling API access in account settings. Check your provider’s plan details and API limits.

How do triggers work for this integration?

The Webhook connector has no native triggers. Start your workflow with a trigger from another app, a Scheduler trigger, or a Webhook-trigger step (if available in your Konnectify plan), then call your target endpoint using a Webhook action.

How do I prevent duplicates?

This connector does not provide a built-in “upsert” action. To avoid duplicates, use one of these patterns:

Lookup first: call a GET endpoint to search, then POST only if no record exists.
Idempotency keys: if the API supports it, send an idempotency header.
Deterministic identifiers: include a stable external ID and update via PATCH/PUT when possible.

What happens if the API rate-limits or returns errors?

If the endpoint returns 429 or transient 5xx errors, use Konnectify retry settings and backoff to reduce failures. If the API provides a Retry-After header, align your retry delays with it when possible.

Can I connect multiple endpoints or accounts?

Yes. You can add multiple Webhook steps in a workflow and configure each with a different URL, header set, or credential value. This is useful for routing data to different environments (dev/staging/prod) or calling multiple services.

How do I send JSON vs form-data, and what headers should I set?

Most modern APIs expect JSON. Set Content-Type: application/json and send a JSON body for POST/PUT/PATCH. For classic form posts, the API may require application/x-www-form-urlencoded or multipart form-data—always follow the destination API’s docs and examples.

Ready to automate your Webhook workflows?

Connect any API endpoint to Konnectify and orchestrate reliable, no-code HTTP automations.

Get started free →