# Setting Up API Integrations
Connect external tools to your Zaphiri Inbox so tasks arrive on their own, without switching apps or copying anything by hand.
> [!quote] Set it up once
> Set up a connection once and let tasks arrive from the tools you already use.
## What are API integrations?
An API integration gives an external tool a secure address for sending tasks to your Zaphiri Inbox. Each integration has its own token, template and delivery log, so you can connect several services separately and review exactly what each one sends.
Common uses:
- Tasks from Zapier, Make or similar no-code tools
- Action items sent from meeting tools or note apps
- Automated tasks from CI/CD pipelines or GitHub Actions
- Custom scripts that send reminders or daily checklists
## Creating an integration
1. Open **Settings** and go to **Integrations**
2. Under **API Integrations**, select **New Integration**
3. Give it a name that identifies the source (for example "GitHub Issues" or "Zapier - Gmail")
4. Set up the **template**. It sets defaults for every task this integration creates:
- **Date mode**: when tasks should be planned (today, a specific date, or unscheduled)
- **Label, project, priority, energy**: applied to all incoming tasks
- **Auto-convert**: skip the Inbox review step and turn items into tasks straight away
- **Group items**: combine several items from one payload into a single task with a checklist
These aren't fixed at creation. You can change every template field later (see [[#Edit the template]] below).
5. Select **Create**
> [!warning] Save your token
> Your API token is shown once, straight after creation. Copy it to a secure place (a password manager or secrets vault) before you close the dialog. If you lose it, you need to rotate the token to get a new one.
## Connecting your external tool
After you create the integration, you have a **webhook URL** in this format:
```
https://tickup-api.mytickup.com/api/v1/inbox/YOUR_TOKEN
```
Paste this URL into your external tool wherever it asks for a webhook endpoint or HTTP POST URL. Each tool has its own setup steps. See [[API Reference/Examples|Examples & Scenarios]] for step-by-step walkthroughs for common tools.
## Managing integrations
### Edit the template
Template settings aren't fixed at creation. Open the integration in **Settings > Integrations > API Integrations** and edit any field (date mode, label, project, priority, energy, auto-convert or grouping) without recreating the integration or its token. Changes apply to tasks created after the update. Tasks already in your Inbox or plan don't change.
### Rotate a token
If a token is ever exposed (shared by mistake or committed to a public repo), rotate it straight away:
1. Find the integration in **Settings > Integrations > API Integrations**
2. Select **Rotate Token**
3. Copy the new token and update your external tool
The old token stops working as soon as you rotate. Update your external service before the next webhook fires.
### Turn an integration on or off
Use the toggle next to any integration to pause it without deleting it. While it is off, incoming requests are rejected. Turn it back on when you're ready to resume.
### View delivery logs
Each integration has a **Webhook Logs** panel showing recent deliveries:
- **Timestamp**: when the request arrived
- **Status**: success, validation error or processing error
- **Error message**: details if something failed
Logs help you debug a new integration or check that a scheduled automation is running correctly.
### Delete an integration
Deleting an integration invalidates its token straight away and removes all its delivery logs. This cannot be undone.
## Good practice
> [!tip] One integration per source
> Create a separate integration for each external tool rather than sharing a single token. This keeps logs clean, lets you turn off one source without affecting the others, and limits exposure if a token needs rotating.
> [!tip] Test before going live
> Use the **Test Webhook** button in the integration panel to send a sample payload. Check your Inbox to confirm a task arrived before you connect your live service.
> [!tip] Use auto-convert for trusted sources
> If an integration sends well-structured, reliable tasks (like a daily checklist), turn on auto-convert so items become tasks straight away and skip the Inbox review step.
---
**See also:** [[Integration Settings]] | [[API Reference]] | [[API Reference/Examples|Examples & Scenarios]] | [[Inbox]]