CI/CD

CI systems can publish custom events to a Felan team. Active team automations decide whether an event starts a session.

Prerequisites

Create a team API key under Settings → API Keys.
Store the key as a protected CI secret.
Create an event automation with the provider, event type, and filters that should match the incoming event.

Event endpoint

POST /api/v1/teams/{teamSlug}/webhooks/events

curl -X POST "https://app.felan.ai/api/v1/teams/${FELAN_TEAM_SLUG}/webhooks/events" \
  -H "Authorization: Bearer ${FELAN_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "event_type": "deployment.completed",
    "provider": "generic",
    "subject": "production",
    "data": {
      "status": "success",
      "commit_sha": "abc123"
    }
  }'

The endpoint returns whether at least one matching automation was dispatched. See Authentication for the current team-key contract.

Provider-native events

GitHub, GitLab, Jira, Linear, Asana, and Vercel have provider-specific webhook handling in Felan. Use those integrations when their signed event flow matches your automation. Use the public team event endpoint for custom CI systems and custom event types. The Vercel connector has provider ID vercel and is configured from the top-level Integrations screen with the webhook secret generated by Vercel.

Getting started

Platform screens

Use cases

Security

Integrations

Prerequisites

Event endpoint

Provider-native events

​Prerequisites

​Event endpoint

​Provider-native events

Prerequisites

Event endpoint

Provider-native events