Customer feedback & Ideas for IRIS

Suggest & prioritise ideas for our customer-driven roadmap

Enable change tracking on the SQL database for key tables so users can fire off triggers based on changes

When attempting to integrate with other cloud based workflow tools such as Microsoft Flow or Zapier, these can fire off any number of actions on the basis of a trigger occurring (e.g. create/modify/delete)

For example, when a new client is created in the database, to create a customer in Xero and pull in address and contact details from the database.

Or when an address of a client is changed in the database, to make the change in Xero too.

Another example, when client created - send off a welcome email automatically 

Or if you want to see what changes were made to client standing data - what was changed (what was the record before and after), who made the change and when was the change made.

Assume that all other technicalities (e.g. integrations and what happens beyond the change being logged in an SQL table) are responsibility of the user. The power of being able to take action from the changes being logged are endless.

 

 

  • Louis Evangelou
  • Mar 11 2019
  • Attach files