Getting Started

​

Prerequisites

• An active Elementum account with access to an organization
• A CloudLink datasource configured in your organization
• Basic understanding of your business process

​

How to Build Your First App

1

Create Your App

Go to Apps in your dashboard and click Create App. During setup you will:

• Connect a CloudLink data source that holds the data your workflow needs
• Set a name, namespace, and handle — the namespace and handle cannot be changed later
• Add a description and category so others in your organization understand what the app does

For the expense approvals example, you’d name the app “Expense Approvals”, connect the CloudLink with your finance data, and set a handle like EXP so every record is identifiable (e.g., EXP-001).For a detailed walkthrough, see the Build an App guide.

2

Design Your Layout and Views

Use the Layout Builder to define what users see and interact with on each record. This includes:

• Adding fields for the data your process requires (e.g., contact info, status, priority, due dates)
• Defining stage-specific sections that control what is visible at each phase of the workflow
• Configuring views — List for scanning and filtering, Board for Kanban-style tracking, and Calendar for date-driven processes
• Creating a form to control how data enters your workflow and which fields are required at submission

For the expense approvals example, your fields might include Employee Name, Department, Expense Amount, Category (travel, software, meals), Description, and Receipt attachment. You’d create a submission form requiring all fields, and use a List view so finance can filter by department or status.

3

Map Your Flow and Add Automations

Open the Flow tab to connect your stages and define how records move through your process. Then layer in automations to make the process run. Key tasks include:

• Defining stages that represent each phase of your business process
• Setting assignment rules to define who owns work at each stage, based on role, workload, or field values
• Adding automations for notifications, field updates, approval routing, and decision-point branching
• Configuring integrations to push data to external systems when key events occur

For the expense approvals example, your stages would be Submit → Manager Review → Finance Processing → Reimbursed (with a Rejected exit path). You’d assign the Manager Review stage to the submitting employee’s manager, and add automations to notify the manager on submission, auto-approve expenses under $50, and flag anything over $500 for VP review.

4

Test and Invite Your Team

Before going live, walk through the entire process yourself and verify everything works end to end:

• Create test records that represent realistic scenarios, including edge cases and branching paths
• Move records through every stage to confirm assignments, field updates, and stage transitions behave correctly
• Check the automation log to verify every automation fired as expected
• Invite a small group of users for feedback and iterate before rolling out to your full team

For the expense approvals example, submit test expenses at different amounts — one under $50 to confirm auto-approval, one over $500 to verify VP routing, and one mid-range to walk through the standard manager review path.

​

Common First Apps

​

Explore More

​

Take Your Workflows on the Go

​

Need Help?

• Documentation: Utilize our comprehensive guides and tutorials to get started.
• Support: Contact our support team to report issues or request features.