> ## Documentation Index
> Fetch the complete documentation index at: https://felan.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# CI/CD

> Send team-scoped CI and deployment events to Felan automations.

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

## Prerequisites

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

## Event endpoint

```text theme={null}
POST /api/v1/teams/{teamSlug}/webhooks/events
```

```bash theme={null}
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](/docs/api-reference/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.