Add action to attach/remove entitlements

[dale-primer-e]

I would like to the option to attach and remove entitlements from licenses in Zapier.

Here is my current workflow.

Trigger: Subscription created in Zoho

• Create user
• Create license choosing policy based on subscription Zoho product code
• Attach or remove entitlements based on Zoho product code
• Update user metadata with license id
• Update subscription in Zoho with license id

I can do everything in KeyGen natively with your integration except for attaching or removing entitlements. I would have to add a webhook to do that. I think adding this might be a valuable feature of this integration.

I see that you do have the option to change/transfer the policy of a license. However, I'm using policies to determine things like whether it's a floating license or an individual license etc. I don't really want to create duplicate policies that differ by entitlements, it seems messy to me when the option to attach/remove entitlements is available, just not natively in Zapier yet.

Is this something you might consider?

[ezekg]

Attach/detach actions for entitlements seems nice for one-offs. Open to a PR, or I'll implement when I get a free bit.

[dale-primer-e]

Thanks Zeke.

Out of curiosity, you say it's good for one offs, what do you mean by that?

Do you think this is a suboptimal way to create licenses in Keygen? Would setting entitlements through policies be better? Or something else?

Wondering if I have missed the intention of Keygen somewhere along the way. I would rather work with the tool than against it, so I'm curious.

[ezekg]

The optimal way to define entitlements would be through various policies, yes. This allows any changes to propagate down to all licenses without having to update the entitlements of every single license, e.g. splitting a general entitlement into 2 fine-grained entitlements: say you have a general PRO entitlement in the beginning, but later on you need to split this into more fine-grained TEAMS and CHAT entitlements. Policy entitlements makes this simple due to propagation.

But there's nothing wrong with attaching entitlements one-off per-license, it just makes maintenance more complex if those entitlements ever need to change, since a change requires every license to be updated.