Stackflows
HomePricingContactBPMN Academy
  • Introduction to StackFlows
  • Getting started
    • 🚀 How to start?
    • ❓FAQ
    • 🤗 Our community
    • 📖 Definitions
    • 📚 Knowledge base
  • Products
    • Studio
      • Collaboration with others
        • Comments
        • Model share
      • Model categories
      • Model design
        • Node types
          • Start node
          • Task
          • User task
            • User task forms (Custom fields)
          • Business rule (DMN) task
          • Service (external) task
          • Call another process
          • End node
          • Gateway
        • Start (Test) process
        • Data mapping
        • Data forms
        • Flow conditions
        • Time formats
        • Token simulation
        • Process real-time simulation
        • General model settings
        • Advanced model settings
      • Model deployment
        • Deployment errors
      • Process execution (Start)
        • Manual process start
        • Process start by email
        • Process start with webhook
        • Process start via API
      • Process execution errors
      • Insights and analytics
        • Model real-time activity
        • Heatmap insights
      • Embedded BPMN Studio
      • Basic features
        • Model versions
        • Version compare
        • Process tags
        • Model import/export
        • Model draft version
        • Model notes
    • App (User area)
      • Dashboard and metrics
      • User tasks
      • Workflows
      • User management
      • Organization structure (Tree)
      • Organization settings
    • Core features
      • Variables
      • Organization (Business) units
      • Tags
      • Profiles
      • Environments
    • Apps & Connectors
      • Make.com integration
      • Custom app integration
      • Camunda 7 connection
      • App & Integration profiles
  • BPMN & DMN modelling
    • Introduction of BPMN
  • API
    • API Introduction
    • API reference
  • Subscriptions & Billing
    • Introduction
  • Troubleshooting
    • How to report a problem?
  • Policies
    • Terms of services
    • Privacy
    • Data processing
Powered by GitBook
On this page
  • Preparation
  • Process specific virtual email box
  • Initiating Process Execution
  • Activity after the process started
  1. Products
  2. Studio
  3. Process execution (Start)

Process start by email

PreviousManual process startNextProcess start with webhook

Last updated 1 year ago

In a SaaS environment, the process starts with an email feature allowing users to trigger process execution by sending an email. This documentation provides a comprehensive guide on how to initiate process execution via email, highlighting the necessary prerequisites and outlining the step-by-step process. By following these instructions, users can seamlessly start processes through email and observe subsequent activity on user or service tasks.

Preparation

Before initiating the process start by email, it is essential to ensure that the desired process model has been successfully deployed within the SaaS platform.

It is important to note that draft versions of process models cannot be started via email. Once the process model is deployed, users can proceed to the Activity mode, which serves as the central hub for real-time process monitoring and execution.

Process specific virtual email box

Within the Activity mode interface, users can locate and click on the play button, which reveals a sidebar containing various process start options. Users should focus on the section titled "Process Start with Email." Here, they will find a dedicated virtual email box unique to the specific process. The structure of this virtual email box is as follows: {{process_uuid}}@{{company_slug}}.stackfl.com. Sending an email to this virtual email box will automatically trigger the start of the associated process.

Each process has a virtual email box: {{process_uuid}}@{{company_slug}}.stackfl.com. For example dd9759e0-cc94-11ed-938f-13cf60270555@acme.stackfl.com

Initiating Process Execution

To initiate process execution via email, users need to compose an email and address it to the designated virtual email box. Things to know:

  • The subject line will not be used.

  • The body of the email can include additional details or attachments required for the process execution and will be automatically converted to a structured JSON file.

  • If the process has mandatory data input requirements during its start, ensure that all the necessary information is added to the email body to initiate the process.

  • All attachments will be stored in your organization storage (it will impact your dedicated storage quota, be sure you don't send heavy files).

  • Once the email is sent, the process associated with the virtual email box will start automatically.

Activity after the process started

After successfully initiating the process execution via email, users can expect to see activity on user or service tasks within the process flow. These tasks represent the specific actions and operations that need to be performed to progress the process further. By monitoring the activity on these tasks, users can gain insights into the progress and status of the process execution.