Troubleshooting Zapier Integration
Common issues and fixes for the SkipUp Zapier integration.
This guide covers the most common issues you might run into when using SkipUp with Zapier, and how to fix them.
Connection issues
Section titled “Connection issues””Authentication failed: Your API key is invalid or expired”
Section titled “”Authentication failed: Your API key is invalid or expired””Your API key is not being accepted. To fix:
- Go to SkipUp Settings > API Keys
- Check that the key you’re using is still active (not revoked)
- If the key was revoked or you’ve lost it, create a new one
- In Zapier, go to My Apps > SkipUp and click Reconnect
- Paste the new key
”Permission denied: API key missing required scope”
Section titled “”Permission denied: API key missing required scope””Your API key doesn’t have all the permissions needed. Different Zap components require different scopes:
| Zap component | Required scopes |
|---|---|
| Triggers (Meeting Scheduled, etc.) | webhooks.read, webhooks.write, meeting_requests.read |
| Schedule Meeting | meeting_requests.write, members.read |
| Cancel / Reassign Meeting | meeting_requests.write |
| Find Meeting Request | meeting_requests.read |
To fix, create a new API key with all required scopes and update your Zapier connection.
Trigger issues
Section titled “Trigger issues”Triggers not firing
Section titled “Triggers not firing”If your Zap isn’t triggering when events happen in SkipUp:
- Check the Zap is turned on — Paused Zaps don’t receive triggers
- Check the webhook is active — Go to SkipUp Settings > Webhooks and look for a
hooks.zapier.comendpoint. Make sure it shows as enabled - Check the Zap history — In Zapier, click your Zap and view Zap History to see if events were received but failed at a later step
- Re-enable the webhook — If the webhook was auto-disabled (after too many failures), re-enable it in SkipUp Settings > Webhooks
”No new data” during trigger testing
Section titled “”No new data” during trigger testing”When testing a trigger, Zapier looks for recent events. If none exist:
- For Meeting Scheduled: Book a test meeting in SkipUp first
- For Meeting Cancelled: Cancel an active request first
- Zapier will offer to use sample data if no recent events are found — this is fine for building your Zap
Action issues
Section titled “Action issues””Invalid organizer: The email you entered is not a member of your SkipUp workspace”
Section titled “”Invalid organizer: The email you entered is not a member of your SkipUp workspace””The organizer email must belong to someone who is a member of your SkipUp workspace. Check:
- The email address is spelled correctly
- The person has been added to your workspace in SkipUp Settings > Members
- Their membership is active (not deactivated)
“Cannot cancel: This meeting request is already cancelled or has been booked”
Section titled ““Cannot cancel: This meeting request is already cancelled or has been booked””Only active meeting requests can be cancelled. If the request was already booked or cancelled, the cancel action will fail. You can add a filter step before the Cancel action to check the meeting status.
”At least one participant email is required”
Section titled “”At least one participant email is required””The Schedule Meeting action requires at least one participant email. Make sure:
- The Participant Emails field is filled in
- If mapping from another app, the field isn’t empty for this particular record
Rate limit errors
Section titled “Rate limit errors”SkipUp allows 120 API requests per minute. In normal Zapier usage, you’re unlikely to hit this. If you do:
- Zapier automatically retries after a short delay
- If it keeps happening, check for duplicate Zaps making the same calls
- Consider adding a Delay step between bulk operations
Webhook issues
Section titled “Webhook issues”Webhook auto-disabled
Section titled “Webhook auto-disabled”If a webhook endpoint accumulates 10 or more failed deliveries in 24 hours, SkipUp disables it. This usually means Zapier had temporary trouble receiving webhooks.
To re-enable:
- Go to SkipUp Settings > Webhooks
- Find the
hooks.zapier.comendpoint - Click Test to verify Zapier can receive webhooks
- If the test succeeds, enable the endpoint
Duplicate triggers
Section titled “Duplicate triggers”If your Zap fires twice for the same event, check:
- You don’t have multiple Zaps with the same trigger
- Each trigger creates a unique webhook — having two “Meeting Scheduled” Zaps creates two webhook endpoints, both of which will fire
Getting more help
Section titled “Getting more help”- Connect SkipUp to Zapier in 5 Minutes — Start from scratch
- Connecting SkipUp to Zapier — Detailed setup and API key guide
- Your First Zap: Form to Meeting — Build your first automation
- How to Write Great AI Context — Get better scheduling emails
- HubSpot + SkipUp — CRM-specific guide
- Salesforce + SkipUp — CRM-specific guide
- Pipedrive + SkipUp — CRM-specific guide
- Check the SkipUp API docs for detailed API reference
- Contact support at [email protected]