Technical Overview

• apps are "registered" to the platform.

• registered apps configure their events, filters, and actions.

• when adding an "event", Spoonity will provide a URL to catch them and you will be provide a name and description.

• when adding a "filter", you will provide a URL that will return a boolean, a name and description, and then configure what inputs your URL will take as a request body.

• when adding an "action", you provide a URL, a name and description, and configure what inputs your URL will take as a request body.

• apps must respond to requests in specific ways.

• apps are distributed within a store in Spoonity.

• vendors can "install" apps from the store. Installing an app will complete an OAuth handshake with the app maintainer linking the vendor's details.

• apps will provide a configuration interface that will be loaded via iFrame within the Spoonity dashboard where vendors can configure the app (like linking social media profiles).

• once installed and configured, apps' events, filters, and actions can be references from the flow builder.