Before you start
An organization owner needs Fellix and Zapier open. You need an API key for the organization you want to automate.
Steps
- In Fellix, open Settings → API keys and select Create key. Enter a Name, choose Static key, and select Webhook subscriptions for triggers and the permissions your Zaps need.
- Select Create key. On Copy your key now, select Copy, then I’ve saved it. The key is shown only once.
- In Zapier, add a Fellix step and paste the key. Build and turn on your Zap.
Permissions
A key belongs to one organization. Choose only the permissions the Zaps need. Write also grants the matching read permission.
What it can do
For example, use a Fellix event to trigger a Zap, or create a client or appointment from another app.
What it will not do
A Zap cannot perform an action without the key’s required permission.
Disconnecting
Turn off the Zap to close its subscription. Revoke the key under Settings → API keys to stop connections using it.
Troubleshooting
“Only the organization owner can manage API keys.” Ask the owner to create the key. If a trigger shows example data, check its read permission; see the reference for the permissions each step needs.
Reference
See the Zapier developer reference for triggers, actions and permissions.