Synchronize Data

The best way to synchronize changes in vPlan to another system is using webhooks.

An alternative would be using a GET list request and filter on the updated_at property.

Pro's and cons:

Subject	Webhooks	Filter on updated_at
Timeliness	✅ are sent out almost instantly	❌ has a delay since data is retrieved e.g. every hour or daily
Deletions	✅ have events to notify on deletions	❌ only shows the current objects
Related objects e.g. a label added to a Card	✅ are available to reflect changes on related objects	❌ the updated_at on base objects is not changed if something is attached
Rate Limit	🟠 Rate Limit is calculated over incoming requests. Webhooks are outgoing requests and thus do not count towards this limit.	🟠 if there are no changes, the requests would be superfluous. Multiple changes could be aggregated between runs
Dependencies	❌ need a webservice to listen to events sent from vPlan	✅ Retrieving data can be done by a simple client with internet

For on premise applications it can be difficult to expose a webservice to receive webhooks.

A possible solution could be to receive webhooks on services like Make.com or Zapier, store the events onto OneDrive, Dropbox or Google Drive, and process these files on the on-premise machine.