Skip to main content
Webhooks deliver events from external systems to Felan. Felan authenticates supported provider deliveries, normalizes each event, and checks the team’s active event automations. Every matching automation starts a Felan session with the event data and the automation’s instructions. A connected integration makes events available, but an event starts work only when an active automation matches its provider, event type, connection, and filters. See Automations to configure what Felan should do when an event arrives.

​
Setup by integration

Webhook setup depends on the provider. The table covers integrations that expose automation events, plus Bitbucket’s current limitation and the generic endpoint. Other integrations in the catalog do not require customer webhook setup for automations.

​
Felan-managed webhooks

​
Asana

After you connect Asana and save the project selection, Felan registers webhooks for those projects automatically. You do not need to copy a webhook URL or secret. Task changes from the selected projects can then match Asana event automations.

​
GitHub

The standard GitHub integration uses Felan-managed webhook delivery. Connect GitHub, authorize the required repositories, and create automations for the GitHub events you want Felan to handle. There is no team-specific webhook URL or secret to copy.

​
Linear

Linear delivers events through Felan’s app-level webhook. Connecting the workspace gives Felan the workspace identity needed to route its events to the correct team. No per-team webhook registration is required.

​
Manual provider setup

​
GitLab

GitLab push and merge-request events use a project webhook with a secret token. Connect GitLab and select the project first. The current team connection screen does not expose the URL and secret required for self-service registration, so contact Felan support before relying on a new GitLab event automation. The OAuth connection alone still provides repository access.

​
Jira Cloud

Jira Cloud issue events require webhook delivery in addition to the Jira Cloud OAuth connection. The current team connection screen does not expose self-service webhook values, so contact Felan support before relying on a new Jira Cloud event automation. The OAuth connection alone still provides issue access.

​
GitHub Enterprise Cloud

After saving a GitHub Enterprise Cloud connector, Felan displays a connector-specific webhook URL and secret.
  1. Copy both values from Integrations.
  2. Add the URL and secret to the webhook settings of the tenant GitHub App.
  3. Subscribe the App only to the events your automations need. Pull-request conversations require issue comments, pull request reviews, and pull request review comments.
  4. Create or enable the matching Felan automations.

​
Jira Server or Data Center

Felan does not register self-hosted Jira webhooks automatically.
  1. Save the Jira Server or Data Center connection.
  2. Copy the team-scoped Webhook URL and Webhook Secret shown in its configuration.
  3. Create a webhook in Jira with those values and select the issue events your automations should receive.
  4. Create or enable automations with the jira-server provider and matching event types.
If you regenerate the secret in Felan, update the Jira webhook before expecting more deliveries.

​
Vercel

Vercel agent access and deployment-event delivery are configured independently under the same integration.
  • Agent access: Connect a narrowly scoped Vercel API token through Nango. Felan exposes it as VERCEL_TOKEN and uses the official CLI for team-list, project-list, project-inspect, deployment-list, and deployment-inspect reads.
  • Deployment events: Register the signed webhook manually:
  1. Open Integrations → Vercel and copy the deployment-event webhook URL.
  2. In Vercel, open Project Settings → Webhooks, create a webhook with that URL, and copy the generated webhook secret.
  3. Save the secret in Felan’s Vercel configuration.
  4. Create or enable automations for the Vercel deployment events you want Felan to handle.
Connecting only Vercel agent access does not enable deployment events. Removing either capability leaves the other active.

​
Bitbucket Server or Data Center

The current Bitbucket Server or Data Center integration supports repository access but does not expose an inbound webhook receiver. Felan does not register Bitbucket webhooks automatically, and there is no manual URL and secret to add to Bitbucket at this time.

​
Generic webhook events

Use the public team event endpoint for CI/CD tools, monitoring systems, test platforms, or any other source that does not have a supported provider webhook flow.

​
Prerequisites

  1. Create a team API key under Settings → API Keys.
  2. Store the key as a protected secret in the sending system.
  3. Create an active event automation whose provider, event type, and filters match the request. If a custom provider or event type is not available in the dashboard picker, create the automation through the REST API with event_provider and event_type.

​
Event endpoint

event_type is required. provider defaults to generic; if you set another provider value, the automation must use the same value. Felan generates id when it is omitted, but send a stable, unique event ID when the source may retry a delivery so Felan can reuse the automation’s idempotency key. The response reports whether at least one matching automation was dispatched. See Authentication for the team API-key contract. The complete request schema is available under Events → Send a team event in the API Reference.

​
Troubleshooting

The provider accepted the webhook but no session started — Confirm that the automation is active and that its provider, event type, connection, and filters match the delivered event. A manual webhook fails authentication — Copy the current URL and secret from Felan. If you rotated a secret, update it in the provider too. A generic event returns 401 Unauthorized — Confirm that the team API key is active, belongs to the team in the URL, and is sent as a bearer token.