Advance Users: Automation Stage [2]

Previously, they were on Manual Stage (Prompts) [1]

Make.com Integration

Dynamic Control

Control Automations from a single place

Context

Prompts (command)

Collaboration

Collaborate with customers without the customer using Make.com

Customers or Collaborators don’t need to login to Make.com

They help to manage the prompts, snippets & docs from a simple UI

The customer can control the context data through Snack Prompt, while the advance user controls the automation architecture without having to share sensitive access to the automation with customer

Scalability

Advance users can now build one automation, that is used by multiple customers

Flow 1: One automation, that saves outputs in different lists (and each customer has access to only that list (therefore, they only see the outputs meant for them, while that same automation is creating outputs for multiple other clients)

Flow 2: One automation, that pulls context data from different lists (so, it can create multiple outputs for different clients from different set of context data)

In short, the advanced user manages one Master automation, but it pulls data from multiple clients, and creates outputs for multiple clients.

Customer Distribution

Automations result in an output, these outputs are usually resulted in: documents, text, files, images and other material meant to be presented for approval or delivered directly to another platform.

When an output is generated by an Automation, Snack Prompt becomes the UI interface that is responsible for delivering the output to a customer or collaborator.