search

TryGhost / Zapier

Ghost <-> Zapier Integration
https://developer.zapier.com/app/1566
MIT License
5 stars 3 forks source link

Improve required action and tips on how to populated member id field #44

Open naz opened 3 years ago

naz commented 3 years ago

Problem

Users are confused about how to use and populate member id field which leads to zap failures

Current behavior

Zapier strips out the entries in the “Required” fields from Zap Templates. Which unfortunately means users need to know which dynamic field they need to use to update a member in Ghost (The Member ID).

Quote from Zapier:

Regarding your ZT, yes users would need to map the required fields. Once they click on the drop-down, they should see a list of options based on their account. This would be a great example for a help doc or quick how-to guide for any future users that might have similar questions. Feel free to send me a link to the ZT if you want to dig into this further.

Quote from John:

I thnk maybe the first time I selected the “Label ID” because that showed up right at the top of the dropdown - the order of the fields that show up is quite confusing - not sure if we have any control over that?

Solution

We should find a good way signaling the users (custom label or some other way) to pick a correct member ID value

naz commented 2 years ago

@royalfig this one seems like more of a cosmetic fix that needs to be done on the UI level of Zapier integration. Could be a good issue to start form as a warm-up :)