How do you deal with subtle differences in usage of terminology? If one service uses the word "ticket" slightly differently than others, how do you deal with that?
We have a raw field from which you can pick anything integration specific.
1. Dealing with custom fields. We provide a way you can map the custom fields specific to the company into the common Model.
2. Dealing with the naming difference Github has issues and Asana has Tasks. We map both the data into a common Ticket model.
This ensures that you integrate with our Ticketing Model and you are integrated to all the Ticketing platforms we support
I think, looking at this, I'd still probably prefer to create something custom. What would really help is simplifying having to set up OAuth and api calls, and just being able to do the mapping (or transform, of extract-transform-load) myself, in case there are edge-cases.
We do the ETL in the background and ensure that the model is completed irrespective of the 1-1 or different entity. You would also be doing the same if you manage the ETL. You could check (https://github.com/poozlehq/poozle/tree/main/integrations/ti...) our ticketing integrations, would love to take some feedback there.
Also if you need more customization you can write on top of the integration we have already (https://github.com/poozlehq/poozle/tree/main/integrations/ti...) and plug it into the platform.