Purpose of guide: This article helps answer common FAQs relating to the Imagine and Zapier integration
Audience: Administrators
TABLE OF CONTENTS
- My Zap stopped after Search for Person. Why?
- I rotated my API key and now my Zaps fail
- Can I use one API key across multiple Zaps?
- Why did my workflow action run under the wrong user?
- Why won’t a Manual Interaction History item save for a person?
My Zap stopped after Search for Person. Why?
This usually means the search step returned no result and the Zap was configured to halt when nothing was found. We recommend that in Zapier you set the "Successful is no search results are found?" option to "True: step run status is "success"" option.
I rotated my API key and now my Zaps fail
This is expected.
When an API key is rotated, the old key is invalidated immediately. Any existing Zap using the old key must be reconnected with the new key.
Can I use one API key across multiple Zaps?
Yes, as long as the key remains valid.
If the key is rotated, every Zap using that key will need to be updated.
Why did my workflow action run under the wrong user?
Zapier actions complete under the System User profile, not the actual user who triggered the Zap. In Imagine workflows, avoid using dynamic values like User who triggered workflow or Workflow Initiator for workflow actions when the action is being driven by Zapier. Instead, set a specific user in the workflow configuration. This is especially important for workflows triggered when a person is added to a manual list or for the manually triggered workflows used in Zapier.
Why won’t a Manual Interaction History item save for a person?
The person must already have the corresponding contact detail on their profile. For example, you cannot add a Personal Email interaction history item unless that person already has a personal email address stored in Imagine. A good pattern is to use Update Person earlier in the Zap to populate the missing contact detail before creating the interaction history record.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article