Here are common issues you might run into while making Zaps, and how to fix them. In addition, Zapier's help center and its support team can also assist with common issues.

My Zap isn't triggering.

If your Zap hasn't fired, check the following:

• Your Zap is turned on. It sounds obvious, but Zaps default to off when you first build them. Go to your Zap and confirm that the toggle in the top-right corner is set to On.
• You're connected to the right Safari Portal account. If you have access to more than one account, make sure the connection in Zapier is pointing to the one where the trigger event happened. You can check this under the trigger step in your Zap editor.
• The trigger event actually occurred after the Zap was turned on. Zapier only picks up events that happen after your Zap is live. For example, if you moved a File before turning the Zap on, that event won't be picked up. Trigger the event again once the Zap is active.
• Your Zap history shows an error. Go to Zap History in your Zapier account and look for any failed runs. Zapier will usually show you exactly which step failed and why.

I don't have any test data showing up.

When setting up a trigger in Zapier, it asks you to load sample data so you can map fields. If nothing shows up, or the data looks stale, it's because Zapier pulls from recent events — and if there haven't been any, there's nothing to pull.

The fix is simple: go to Safari Portal and actually perform the action you want to test. If you're setting up a File Moved to Stage trigger, manually move a real file to that stage. If it's a Traveler Added trigger, add a traveler to a file. Then go back to Zapier and click "Find new records" — your event will appear.

My Zap fires, but the data is missing or incorrect.

If your Zap runs but a field is empty or showing the wrong value, the most likely cause is one of the following:

• The field wasn't mapped correctly. Open the action step in your Zap editor and check that each field is mapped to a value from the trigger — not left blank or accidentally set to a fixed value.
• The field was empty in Safari Portal when the trigger fired. Zapier can only pass data that exists on the record at the moment the trigger fires. If a field like trip dates or consultant name wasn't filled in yet, it will come through blank. Make sure your File or Contact in Safari Portal is complete before the trigger fires, or add a Zapier filter to only proceed when key fields are present.
• You're looking at an old test run. Zapier's Zap History can show previous runs that used incomplete test data. Check the most recent run to see the current state.

My action isn't completing; Safari Portal won't create or update what I want.

If your Zap runs but the action step fails, check the following:

• Required fields are missing. Some Safari Portal actions require certain fields to be present — for example, Create File requires a file name. Open the failed task in Zap History, read the error message, and check which field is missing.
• Your Safari Portal connection has expired. Zapier connections occasionally need to be re-authenticated. Go to the Connected Accounts section in Zapier, find Safari Portal, and reconnect it.
• The record you're trying to update doesn't exist. If you're using Update File or Update Contact, Zapier needs to find an existing record first. Make sure you have a Find File or Find Contact step earlier in your Zap, and that it's returning a result before the update step runs.

I'm getting duplicate contacts or files.

Duplicates are almost always caused by a Zap running multiple times on the same event, or by missing a "find before create" step.

Before creating a new contact or file, add a Find Contact or Find File search step to your Zap. If the record already exists, Zapier can use the existing one instead of creating a new one. Use Zapier's built-in "Find or create" option to handle this automatically.

If you're seeing duplicates because the same trigger is firing repeatedly, check your Zap History to see how many times it ran and what caused each run.

I think something is wrong on the Safari Portal side.

If you've worked through the steps above and your Zap is still not behaving as expected, it may be a bug rather than a configuration issue.

Before submitting the bug, check:

• Whether the issue is consistent (does it happen every time, or just occasionally?)
• Which trigger or action is involved
• What Zapier's error message says, if there is one

Then submit a report using the Zapier feedback and bug form, and the team will investigate. If you'd prefer to talk it through, you can book a Zapier support call with the team using the same link.