Zapier Troubleshooting
Authentication Errors
Invalid API Key
Symptom: Zapier shows "Invalid API Key" or "Authentication failed" when connecting.
Solutions:
- Verify you copied the full key (must start with
ctza_) - Generate a new key at Configuración → Integraciones → Claves API
- Make sure there are no spaces before or after the key
- If you regenerated the key, update the connection in Zapier: go to My Apps → Cotizera → Reconnect
Expired Key
Symptom: A working Zap stops running with an authentication error.
Solutions:
- Go to Configuración → Integraciones → Claves API and check your key's status
- If expired, generate a new one and reconnect in Zapier
- Consider creating keys without an expiration date for long-running integrations
Insufficient Permissions
Symptom: "Forbidden" or "Insufficient permissions" error on specific actions.
Solutions:
- Verify your API key has the required permissions (read, write)
- Only users with the OWNER role can generate API keys with full permissions
- COLLABORATOR users have limited access — contact your account administrator
Trigger Not Firing
Basic Checks
- Is the Zap turned on? — Verify the Zap toggle is ON (green)
- Did the event occur after activating the Zap? — Zaps don't capture events that happened before activation
- Is the event type correct? — If you configured "Quote Status Changed" but created a new quote, the trigger won't fire
Trigger Can't Find Sample Data
Symptom: When setting up the trigger, Zapier says "We couldn't find any samples".
Solutions:
- Create a test record in Cotizera (a quote, client, or product depending on the trigger)
- Click "Find new records" in Zapier
- If it still doesn't work, verify your API key has read permissions
Execution Delay
Symptom: The Zap runs but with a delay.
Explanation: Zapier checks triggers every 1-15 minutes depending on your plan:
- Free plan: every 15 minutes
- Starter: every 15 minutes
- Professional: every 2 minutes
- Team/Company: every 1 minute
For instant execution, set up webhooks in Cotizera pointing to a Zapier Catch Hook instead of using native triggers.
Action Errors
Missing Required Fields
Symptom: "Missing required field" error when running an action.
Solutions:
- Review the required fields table in the integration guide
- For Create Quote, you need
clientIdanditems— use the "Find Client" search to get the ID - For Create Client, you need
nameandemail - For Create Product, you need
nameandprice
Invalid Client or Product ID
Symptom: "Client not found" or "Product not found" error.
Solutions:
- Use Cotizera searches ("Find Client", "Find Product") in a previous step to get valid IDs
- Don't use IDs from other tools (like HubSpot) — Cotizera IDs are internal
- Verify the client/product hasn't been deleted
Rate Limiting
Symptom: Error 429 "Too Many Requests".
Explanation: Cotizera allows 30 requests per minute per API key.
Solutions:
- If you have high-volume Zaps, space out executions using Delay by Zapier
- Use a different API key for each high-traffic Zap
- Contact support if you need a higher limit
Common Error Codes
| Code | Error | Description | Solution |
|---|---|---|---|
| 401 | Unauthorized | Invalid or expired API key | Regenerate API key and reconnect |
| 403 | Forbidden | No permission for the operation | Check API key permissions |
| 404 | Not Found | Resource doesn't exist | Verify client/product IDs |
| 409 | Conflict | Duplicate resource | A record with that data already exists |
| 422 | Validation Error | Invalid request data | Review field formats |
| 429 | Rate Limited | Too many requests | Wait 1 minute or space out requests |
| 500 | Server Error | Internal Cotizera error | Retry in a few minutes |
Debugging Steps
1. Check Zapier Task History
- Go to zapier.com/app/history
- Find the failed execution
- Click to see each step's details
- The failed step will show the error message and data sent
2. Check Cotizera Activity Log
- Go to Configuración → Actividad in Cotizera
- Filter by "API" to see API requests
- Look for errors around the time of the Zap failure
- The log shows the endpoint, method, response code, and error details
3. Verify API Key Permissions
- Go to Configuración → Integraciones → Claves API
- Verify the key used in Zapier is active
- Check assigned permissions (read, write, admin)
4. Test the API Directly
If the issue persists, test the Cotizera API directly with cURL:
# Verify authentication
curl -H "Authorization: Bearer ctza_your_key_here" \
https://cotizera.com/api/v1/quotes
# Create a test client
curl -X POST https://cotizera.com/api/v1/clients \
-H "Authorization: Bearer ctza_your_key_here" \
-H "Content-Type: application/json" \
-d '{"name": "Test Client", "email": "test@example.com"}'If the API responds correctly but Zapier fails, the issue is in the Zap configuration.
5. Reconnect the Account
If nothing works, disconnect and reconnect your Cotizera account in Zapier:
- Go to zapier.com/app/connections
- Find "Cotizera"
- Click "Reconnect"
- Enter your updated API key
Getting Help
If the issue persists after following this guide:
- Email: soporte@cotizera.com
- Documentation: See the Zapier Integration and Webhooks guides
- Zapier Support: For Zapier-specific issues, contact support.zapier.com
When contacting support, include the error code, Zap ID, and a screenshot of Zapier's task history.