# flow2act · Integration erstellen

Benannte ausgehende Verbindung anlegen. E-Mail-Trigger werden über Flow-Entwürfe verwaltet.

kind=email benötigt config.recipientDomains. teams benötigt eine Microsoft-Teams-Workflows-HTTPS-URL; http erlaubt HTTPS und optional authorization. Separates Anlegen von email_inbound liefert EMAIL_TRIGGER_DESIGNER_REQUIRED. Lege stattdessen einen Flow-Entwurf mit start.trigger={kind:email,integrationId:null} an oder speichere ihn. Nach dem TXT-Nachweis einer Absenderdomain entsteht seine Adresse atomar. Kunden benötigen keinen Gateway-Schlüssel.

## POST /v1/integrations

Authentication: FLOW2ACT_ACCESS_TOKEN from flow2act sign-in
Required tenant header: X-Organization-Id.
Required user permissions: Administrator oder Sandbox-Entwickler erforderlich. The API checks current membership, roles, key scopes and resource permissions on every request. Documentation visibility grants no access.

## Input parameters
- name (string, required): min length 1 · max length 80
- kind (string, required): email | teams | http | email_inbound
- active (boolean, optional): default true
- config (object, required): 

## Request example (replace example IDs)

```sh
curl -X POST "https://api.flow2act.com/v1/integrations" \
  -H "authorization: Bearer $FLOW2ACT_ACCESS_TOKEN" \
  -H "x-organization-id: 10000000-0000-4000-8000-000000000001" \
  -H "idempotency-key: example-create-integration-001" \
  -H "content-type: application/json" \
  --data-raw '{
  "name": "Purchasing HTTP",
  "kind": "http",
  "active": true,
  "config": {
    "url": "https://example.com/flow-events"
  }
}'
```

Source: /docs/create-integration
Full schemas: /docs/openapi.json