Skip to main content
This comprehensive reference guide covers all available actions in Elementum’s automation system. Each action includes a description, example usage, and common use cases to help you build sophisticated automations.
Looking to understand automation concepts? Start with the Automation System guide to learn about event-driven automation and AI integration.

​
Logic Actions

Logic actions control the flow and decision-making in your automations.
Purpose: Evaluate conditions and execute actions only when the condition is true.How it works: Creates a decision point in your automation where subsequent actions only run if the specified condition is met.Example:
IF customer_tier = "Enterprise"
  → Send Message to Teams (priority channel)
  → Make Assignment (senior agent)
Common Use Cases:
  • Route high-value customers to priority support
  • Apply different approval processes based on amounts
  • Trigger escalations for critical issues
  • Customize responses based on customer type
Variables: Outputs boolean result that can be referenced by other actions
Purpose: Provide alternative logic paths when the initial IF condition is false.How it works: Creates multiple conditional branches, allowing complex decision trees in your automation.Example:
IF order_amount > $10,000
  → Start Approval Process (CFO approval)
OTHERWISE IF order_amount > $1,000
  → Start Approval Process (manager approval)
OTHERWISE
  → Update Record Fields (auto-approved)
Common Use Cases:
  • Multi-tier approval workflows
  • Customer service routing based on multiple criteria
  • Pricing logic with different discount tiers
  • Escalation procedures with multiple levels
Variables: Outputs boolean result for each branch condition
Purpose: Execute a set of actions for each item in a collection or list.How it works: Loops through a collection of records or data, performing the same actions on each item.Example:
Search Records (today's orders) → Repeat for Each order:
  → Run Calculation (shipping cost)
  → Update Record Fields (add shipping)
  → Send Email Notification (shipping confirmation)
Common Use Cases:
  • Process multiple orders simultaneously
  • Send notifications to multiple users
  • Update multiple records with the same information
  • Generate reports for multiple departments
Variables: Provides access to current item in loop and loop iteration count

​
Record Actions

Record actions manage data creation, updates, and relationships within your system.
Purpose: Add new records to your tables automatically.How it works: Creates a new record with specified field values, often using data from triggers or previous actions.Example:
Email Received → Create Record (Support Ticket)
  → Fields: Subject, Customer Email, Priority, Description
  → Result: New support ticket ready for assignment
Common Use Cases:
  • Generate support tickets from emails
  • Create project records for new customers
  • Log activities and interactions
  • Generate invoices from completed orders
Variables: Outputs new record ID and all field values for use in subsequent actions
Purpose: Modify existing record data with new information.How it works: Changes field values in existing records, often using data from AI analysis or calculations.Example:
AI Classification → Update Record Fields (Lead Record)
  → Fields: Lead Score, Priority, Qualification Status
  → Result: Lead record updated with AI insights
Common Use Cases:
  • Update customer information from external sources
  • Change order status as it progresses
  • Apply AI-generated classifications to records
  • Update project progress and milestones
Variables: Outputs updated record with new field values
Purpose: Find records that match specific criteria.How it works: Queries your data to find records meeting certain conditions, returning matching results.Example:
Search Records (Customers)
  → Criteria: Email = trigger.sender_email
  → Result: Customer record for follow-up actions
Common Use Cases:
  • Find customer records from email addresses
  • Locate related orders or projects
  • Identify overdue tasks or activities
  • Find records needing attention or updates
Variables: Outputs matching records with all field data accessible
Purpose: Create connections between different records.How it works: Establishes relationships between records, enabling data connections and workflows.Example:
Create Record (Project) → Relate Records
  → Link: New Project → Customer Record
  → Result: Project connected to customer for tracking
Common Use Cases:
  • Link projects to customers
  • Connect orders to customer accounts
  • Associate support tickets with products
  • Create document relationships
Variables: Outputs relationship details and connected record information
Purpose: Initiate approval workflows for records requiring authorization.How it works: Begins an approval process with designated approvers and workflow steps.Example:
Create Record (Purchase Order) → Start Approval Process
  → Approver: Manager (if < $5,000), CFO (if > $5,000)
  → Result: Approval workflow begins with notifications
Common Use Cases:
  • Purchase order approvals
  • Document review processes
  • Budget approval workflows
  • Policy exception requests
Variables: Outputs approval process ID and current status
Purpose: Automatically assign records or tasks to appropriate team members.How it works: Routes work to specific users based on criteria like workload, expertise, or availability.Example:
AI Classification → Make Assignment
  → IF category = "Technical" → Assign to Technical Team
  → IF category = "Billing" → Assign to Billing Team
Common Use Cases:
  • Route support tickets to appropriate teams
  • Assign leads to sales representatives
  • Distribute work based on expertise
  • Balance workloads across team members
Variables: Outputs assigned user information and assignment details
Purpose: Add users to monitor record changes and updates.How it works: Subscribes users to receive notifications when records are modified.Example:
Create Record (High Priority Issue) → Add Watcher
  → Watcher: Department Manager
  → Result: Manager receives updates on issue progress
Common Use Cases:
  • Keep managers informed of critical issues
  • Notify stakeholders of project changes
  • Alert team members to important updates
  • Maintain oversight on sensitive matters
Variables: Outputs watcher details and notification preferences
Purpose: Prevent changes to specific record fields.How it works: Applies field-level restrictions to maintain data integrity.Example:
Approval Process Complete → Record Field Locking
  → Lock: Price, Terms, Approval Status
  → Result: Critical fields protected from changes
Common Use Cases:
  • Lock approved contract terms
  • Protect financial calculations
  • Secure completed approval decisions
  • Maintain audit trail integrity
Variables: Outputs locking status and protected field list
Purpose: Modify the status of approval processes.How it works: Changes approval workflow status based on decisions or conditions.Example:
Manager Decision → Update Approval Status
  → Status: Approved/Rejected/Pending
  → Result: Workflow advances to next step
Common Use Cases:
  • Process manager decisions
  • Handle approval timeouts
  • Update workflow progress
  • Trigger post-approval actions
Variables: Outputs new approval status and workflow state

​
Communication Actions

Communication actions manage notifications, messages, and team collaboration.
Purpose: Send professional emails to up to 25 recipients as part of your workflow, with optional file attachments.How it works: Delivers formatted emails with dynamic content using variables from your automation.Example:
Support Ticket Created → Send Email Notification
  → To: Customer, Account Manager
  → Subject: "Ticket #{{ticket_number}} - {{issue_summary}}"
  → Content: Professional acknowledgment with next steps
  → Attachments: Generated report PDF
Configuration:
FieldDescription
Action NameA descriptive name for this action
From Display NameThe sender name that appears to recipients
FromThe email address prefix (before @yourdomain.com)
BccRecipients to blind carbon copy (up to 25 total recipients)
SubjectEmail subject line
Notification BodyEmail content with HTML formatting
Email AttachmentsOptional files to include with the email
Email Attachments:You can attach files from multiple sources to your email. Select one or more attachment sources:
Attachment TypeDescription
RecordAttach files from specific file fields on the trigger record. Select which file fields to include.
AttachmentsAttach all files from the attachments block on the trigger record. Useful when users have uploaded supporting documents.
FileAttach files from file fields available in the workflow context.
You can combine multiple attachment types in a single email. For example, attach both a generated report and files from the record’s attachments block.
Total attachment size is limited to 25MB. If attachments exceed this limit, the email will fail to send.
Features:
  • Multiple recipients (up to 25)
  • HTML formatting support
  • Dynamic content with variables
  • Attachment capability
  • Professional templates
Common Use Cases:
  • Customer confirmations and updates
  • Team notifications and alerts
  • Executive summaries and reports
  • Process completion notifications
For transactional emails only. Marketing use may result in restrictions or loss of access.
Variables: Outputs email delivery status and recipient information
Purpose: Send real-time messages to Microsoft Teams channels.How it works: Integrates with Teams to deliver instant notifications to team collaboration spaces.Example:
High Priority Alert → Send Message to Teams
  → Channel: #critical-alerts
  → Message: "🚨 Critical issue: {{issue_description}} - Customer: {{customer_name}}"
Common Use Cases:
  • Critical issue alerts
  • Team coordination messages
  • Progress updates and milestones
  • Urgent escalations
Variables: Outputs message delivery status and channel information
Purpose: Add comments to records for documentation and audit trails.How it works: Creates timestamped comments on records to document automation actions and decisions.Example:
AI Classification → Post Comment
  → Comment: "AI classified as {{category}} with {{confidence}}% confidence"
  → Result: Automated documentation of AI decision
Common Use Cases:
  • Document automation decisions
  • Log process milestones
  • Track approval reasoning
  • Maintain audit trails
Variables: Outputs comment ID and timestamp for reference

​
File Actions

File actions process documents, extract information, and manage file operations.
File Size Limits: The Elementum system supports file uploads up to 250MB per file. This applies to all file operations including attachments, file fields, and API uploads. Note that email attachments have a lower limit of 25MB due to email service provider restrictions.
Purpose: Extract text content from uploaded files.How it works: Processes various file formats to extract readable text for further automation processing.Supported Formats: PDF, DOC, DOCX, TXT, CSV, ExcelExample:
Attachment Added → Read File
  → Input: Uploaded contract PDF
  → Output: Full text content for analysis
Common Use Cases:
  • Extract content from contracts
  • Process uploaded reports
  • Read customer communications
  • Import data from documents
Variables: Outputs file content as text and file metadata
Purpose: Use AI to analyze documents and extract key information intelligently.How it works: AI understands document context and extracts relevant structured data automatically.Example:
Contract Upload → AI File Analysis
  → Analysis: Extract parties, dates, terms, obligations
  → Result: Structured contract data for tracking
Analysis Types:
  • Contract Analysis: Parties, dates, terms, obligations
  • Invoice Processing: Vendor, amount, line items, due dates
  • Resume Screening: Skills, experience, education
  • Report Analysis: Key metrics, trends, insights
Common Use Cases:
  • Automated contract processing
  • Invoice data extraction
  • Resume screening
  • Document classification
Variables: Outputs structured data extracted from document
Purpose: Process multiple files simultaneously.How it works: Handles batch file processing for efficiency when dealing with multiple documents.Example:
Multiple Files Uploaded → Read Bulk File
  → Process: All monthly reports
  → Result: Combined data from all files
Common Use Cases:
  • Process monthly report batches
  • Handle multiple customer uploads
  • Batch document processing
  • Archive file analysis
Variables: Outputs array of file contents and processing results
Purpose: Save files as attachments to specific records.How it works: Associates files with records for organized document management. This action is required to attach generated reports, email attachments, or other files from automation workflows to records. Files are stored in the attachments block of the record, separate from file field types.
Save generated reports: Use this action after the Generate Report action to attach the generated report file to a record. Without this action, generated reports exist only as temporary references within the automation and are not saved.
Important for email attachments: When an email includes multiple attachments, you must use a Repeat for Each action to save each attachment one by one. This action processes one file at a time, so the loop lets you handle each attachment separately.
Example:
Email with PDF → Repeat for Each (attachment)
  → Save Attachment
  → Attach to: Customer Record
  → Result: Each document stored with customer
Generate Report Example:
Month End Trigger → Generate Report (Monthly Summary)
  → Save Attachment (attach report to company record)
  → Send Email Notification (with report as attachment)
  → Result: Report saved to record and emailed to stakeholders
Ways Files Get Added to Records:Files can be added to records through multiple methods:
MethodDescriptionMax Size
Email ReceivedWhen creating records via “Email Received” trigger, any email attachments are automatically added to the record250MB per file
Send API RequestDownload files from external APIs using the Send API Request action and save them as attachments250MB per file
External APIThird-party systems can add attachments via the Elementum API endpoints250MB per file
Manual UploadUsers can manually add attachments in the record layout’s attachments block250MB per file
File FieldsSpecific File Field types on records for storing files in designated fields (different from attachments block)250MB per file
Common Use Cases:
  • Save generated reports to records
  • Save contracts with customer records
  • Attach invoices to orders
  • Store documentation with projects
  • Organize file submissions from email or uploads
  • Archive email attachments to records
Variables: Outputs attachment details and storage location
Purpose: Extract files from compressed archives.How it works: Processes ZIP files to access contained documents for further processing.Example:
ZIP File Uploaded → Unzip File
  → Extract: Monthly reports and data files
  → Result: Individual files ready for processing
Common Use Cases:
  • Process batch document uploads
  • Handle archived file submissions
  • Extract backup file contents
  • Bulk document processing
Variables: Outputs list of extracted files and their contents

​
Data Actions

Data actions perform calculations, transformations, and AI-powered data processing.
Purpose: Execute mathematical operations and business calculations.How it works: Performs calculations using record data and variables to generate computed values.Example:
Order Created → Run Calculation
  → Calculate: (Subtotal × Tax Rate) + Shipping
  → Result: Total order amount with taxes
Common Use Cases:
  • Calculate pricing and taxes
  • Compute discounts and fees
  • Determine shipping costs
  • Analyze financial metrics
Variables: Outputs calculated values for use in other actions
Purpose: Use AI to clean, normalize, and enhance data automatically.How it works: AI analyzes data patterns and applies intelligent transformations for consistency.Example:
Customer Data Import → Transform Data with AI
  → Transform: Standardize addresses, format phone numbers
  → Result: Clean, consistent customer data
Transformation Types:
  • Address Standardization: “123 main st” → “123 Main Street”
  • Phone Formatting: “5551234567” → “(555) 123-4567”
  • Company Name Matching: “Microsoft Corp” → “Microsoft Corporation”
  • Date Normalization: Various formats → Standard format
Common Use Cases:
  • Clean imported data
  • Standardize customer information
  • Normalize addresses and contacts
  • Format business data consistently
Variables: Outputs transformed data in standardized format
Purpose: Automatically categorize and classify data using AI.How it works: AI analyzes content and assigns appropriate categories, tags, or classifications.Example:
Support Email → AI Classification
  → Analysis: Email content and context
  → Result: Category (Bug, Feature Request, General Support)
Classification Types:
  • Support Ticket Categorization: Bug, Feature, Support
  • Lead Qualification: Hot, Warm, Cold
  • Document Classification: Contract, Invoice, Report
  • Content Analysis: Sentiment, Priority, Topic
Common Use Cases:
  • Categorize support tickets
  • Classify lead quality
  • Organize documents
  • Analyze customer sentiment
Variables: Outputs classification results and confidence scores
Purpose: Generate concise summaries of lengthy content.How it works: AI analyzes long-form content and extracts key points into digestible summaries.Example:
Long Customer Feedback → AI Summarization
  → Analysis: Extract key points and sentiment
  → Result: Executive summary for leadership
Summarization Types:
  • Executive Summaries: Key business points
  • Technical Summaries: Main technical details
  • Customer Feedback: Sentiment and main concerns
  • Report Summaries: Key metrics and findings
Common Use Cases:
  • Summarize customer feedback
  • Create executive briefings
  • Digest long reports
  • Extract meeting highlights
Variables: Outputs summary text and key extracted points
Purpose: Store values for use in subsequent automation actions.How it works: Creates named variables that can be referenced throughout your automation workflow.Example:
Run Calculation → Set Variable
  → Variable Name: discount_amount
  → Value: ${{calculated_discount}}
  → Usage: Apply discount in subsequent actions
Common Use Cases:
  • Store calculation results
  • Save API response data
  • Cache frequently used values
  • Create dynamic content
Variables: Creates the specified variable for use in later actions

​
Agent Actions

Agent actions enable AI agents to perform proactive outreach and interactions.
Purpose: Trigger automated phone calls from agents to customers or users as part of your workflow.How it works: Initiates an outbound phone call asynchronously where a configured AI agent will conduct the conversation. The workflow continues immediately without waiting for the call to complete, using a fire-and-forget execution model.Configuration:
  • Action Name: Descriptive name for the call action
  • AI Agent: Which agent will conduct the call
  • Phone Service: Phone service provider to place the call
  • Phone Number: Number to call (from record field, previous task output, or static value)
  • Related Record (optional): Record this call relates to for context
  • Additional Context (optional): Extra information for the AI agent
  • Default Language: Language for the call conversation
Example:
High Priority Ticket Created → Initiate Call
  → Agent: Support Agent
  → Phone Number: {{customer.phone}}
  → Context: "Follow up on ticket {{ticket_number}}"
  → Result: Agent calls customer while workflow continues
Common Use Cases:
  • Automated appointment reminders
  • Follow-up calls for high-priority support tickets
  • Proactive customer outreach for critical updates
  • Emergency notifications requiring immediate contact
  • Post-purchase satisfaction checks
Fire-and-Forget Execution: The workflow does not wait for the call to complete. Use the “Agent Conversation Ended” trigger in a separate automation to process call outcomes.Variables: Outputs call initiation status and call ID for reference
Purpose: Enable AI agents to autonomously complete complex tasks within automation workflows, bridging structured and unstructured processes.How it works: Hands off the workflow to an AI agent with context and success evaluation criteria. The agent works proactively to accomplish the task in a headless environment, then returns structured output that subsequent automation actions can use. This bridges deterministic automation steps with intelligent, autonomous task completion.Configuration:
  • Action Name: Descriptive name for the agent task action
  • AI Agent: Select an existing agent or create a new one for the task
  • Task Definition: Clear description of what the agent should accomplish with success evaluation criteria to guide autonomous actions (supports value references)
  • Output Type: Choose how the agent returns data:
    • Text: Simple text response from the agent
    • Structured: Define specific output fields (like AI File Reader) for structured data extraction
  • Output Fields (Structured mode): Define the exact fields you want returned with field names and types
  • Test & Preview: Try out the agent task with real values for any value references to validate output before deployment
Example:
Order Approved → Run Agent Task
  → Agent: Research Agent
  → Task: "Research customer {{customer.company}} industry trends and competitive landscape. Success: Provide 3-5 key insights relevant to their business"
  → Output Type: Structured
  → Fields: key_insights (list), competitive_threats (text), opportunities (text)
  → Result: Structured insights available for subsequent actions
Workflow Pattern - Structured to Unstructured to Structured:
Record Updated (structured) → 
  Run Agent Task (autonomous intelligence) → 
  Update Record Fields (structured output) → 
  Send Email Notification (structured)
Common Use Cases:
  • Research and analysis tasks requiring intelligence and judgment
  • Complex decision-making beyond simple classification rules
  • Data enrichment requiring external research or synthesis
  • Quality assessment and content evaluation tasks
  • Multi-step problem solving with proactive action
  • Competitive intelligence gathering and analysis
Headless Environment: The agent operates without user interaction. Task definitions must be clear and self-contained with all necessary context provided through value references.Error Handling: Built-in retry logic (up to 3 attempts) if the agent doesn’t provide output in the expected format, with error messages passed back to help the agent correct structured output.Agent Deletion Protection: When attempting to delete an agent used in automations, you’ll see which automations depend on it with direct links.Variables: Outputs structured data from the agent task:
  • run_agent_task.success - Boolean indicating task completion
  • run_agent_task.error_message - Text field with any error details
  • run_agent_task.{custom_fields} - Any custom output fields defined in configuration
Import/Export: Automations with Run Agent Task actions can be exported and imported across apps seamlessly.
For a comprehensive guide on leveraging this action to bridge structured and unstructured workflows, see the Agent Task Automation Guide.

​
User Actions

User actions manage user searches and assignments within your system.
Purpose: Find users within your system based on criteria.How it works: Queries user database to find appropriate team members for assignments or notifications.Example:
Technical Issue → Search Users
  → Criteria: Department = "Engineering", Available = true
  → Result: Available engineers for assignment
Search Criteria:
  • Department or team
  • Skills and expertise
  • Availability status
  • Location or time zone
  • Role or permissions
Common Use Cases:
  • Find appropriate agents for assignments
  • Locate subject matter experts
  • Identify available team members
  • Route based on expertise
  • Look up users by email for automated assignment
Variables:The Search Users action outputs the following value references for use in subsequent actions:
VariableTypeDescription
usersUser (array)All users matching the search criteria
userUserThe first user found (convenient for single-user lookups)
countNumberTotal count of users matching the criteria
Accessing User Properties:For the single user output, you can access the following sub-properties directly:
Sub-PropertyTypeDescription
user.idUser IDThe unique identifier of the user
user.nameTextThe user’s display name
user.emailTextThe user’s email address
etc etc.
To access individual user properties from the users array (all found users), use a Repeat for Each action to iterate over the collection. Inside the loop, each item will have access to the user sub-properties like item.id, item.name, and item.email.

​
External Actions

External actions integrate with external systems and services.
Purpose: Connect with external systems through API calls.How it works: Makes HTTP requests to external services to retrieve or send data, with support for multiple authentication methods.Example:
Order Created → Send API Request
  → Endpoint: Inventory Management System
  → Request: Check stock levels for order items
  → Result: Current inventory status
Request Types:
  • GET: Retrieve data from external systems
  • POST: Send data to external services
  • PUT: Update external system records
  • DELETE: Remove data from external systems
Authorization Types:
TypeDescription
No AuthNo authorization header is added to the request
Basic AuthUsername and password encoded as Base64 in the Authorization header
Bearer TokenToken-based authentication with static or dynamic token values
OAuthClient Credentials flow with automatic token caching and refresh
Basic Auth:Enter a username and password. These credentials are encrypted at rest and sent as a Base64-encoded Authorization header with each request.Bearer Token:Two options for providing the token:
OptionDescription
Static TokenEnter a fixed token value (encrypted at rest)
Dynamic ReferenceSelect a value from a previous action or trigger output using the reference picker (📎)
The dynamic reference option enables advanced authentication patterns like JWT tokens generated by a prior action.OAuth (Client Credentials):Implements the OAuth 2.0 Client Credentials flow:
  • OAuth URL: The token endpoint URL
  • Client ID: Your OAuth client identifier (encrypted at rest)
  • Client Secret: Your OAuth client secret (encrypted at rest)
  • Request Type: How credentials are sent:
    • HTTP Basic: Credentials in Authorization header
    • Form URL Encoded: Credentials in request body
  • Custom Headers: Additional headers for the token request (optional)
Tokens are automatically cached and refreshed before expiration.Common Use Cases:
  • Check inventory levels
  • Validate addresses
  • Process payments
  • Update CRM systems
  • Sync with accounting software
  • Integrate with REST APIs requiring various authentication methods
Variables:
VariableTypeDescription
responseJSONParsed JSON response body
successBooleanWhether the request succeeded
textResponseTextRaw text response body
statusCodeNumberHTTP status code (e.g., 200, 404, 500)
fileFileDownloaded file (when response type is FILE)
Purpose: Execute custom business logic and specialized processing.How it works: Runs custom functions when built-in actions don’t meet specific requirements.Example:
Complex Data → Run Function
  → Function: Custom pricing algorithm
  → Input: Customer data, order details
  → Result: Specialized pricing calculation
Function Types:
  • Custom Calculations: Specialized business logic
  • Data Processing: Complex transformations
  • External Integrations: Custom API handling
  • Analytics: Advanced data analysis
Common Use Cases:
  • Complex pricing calculations
  • Specialized data processing
  • Custom integrations
  • Advanced analytics
Variables: Outputs function results and computed values

​
Workflow Actions

Workflow actions manage automation processes and system interactions.
Purpose: Create reports based on data criteria and analysis, generating a file reference that can be used in subsequent automation actions.How it works: Compiles data into formatted reports (Excel or PDF). The report is created as a file value that can be referenced by other actions in the same automation, such as sending via email or saving to a record.
Important: The Generate Report action does NOT automatically save the report to a record. The report exists only as a value reference within the automation workflow. To attach the generated report to a record, use the Save Attachment action after generating the report.
Example:
End of Month → Generate Report
  → Report Type: Sales Performance Summary
  → Data: Monthly sales, targets, performance metrics
  → Save Attachment (to save the report to a record)
  → Result: Report file available for use in subsequent actions
Report Types:
  • Performance Reports: Sales, productivity, efficiency
  • Status Reports: Project progress, system health
  • Compliance Reports: Audit trails, regulatory data
  • Analytics Reports: Trends, insights, predictions
Common Use Cases:
  • Monthly performance summaries that are emailed to stakeholders
  • Project status reports saved to project records
  • Compliance documentation attached to audit records
  • Executive dashboards sent via Teams or Email
Workflow Pattern:To save a generated report to a record, combine actions:
Trigger → Generate Report → Save Attachment
  → Result: Report is generated and attached to the specified record
Variables:The Generate Report action outputs a file reference that can be used in subsequent actions:
VariableTypeDescription
generated_reportFileThe generated report file (Excel or PDF) that can be used in Save Attachment, Send Email, or other file-accepting actions

​
Quick Action Categories

Logic & Control

If, Otherwise If, Repeat for Each

Data Management

Create, Update, Search, Relate Records

Communication

Email, Teams Messages, Comments

File Processing

Read, AI Analysis, Bulk Processing

AI Intelligence

Classification, Summarization, Data Transform

Agent Actions

Initiate Call

External Integration

API Requests, Custom Functions

​
Getting Started with Actions

  1. Choose Your Trigger: Start with an event that matters to your business
  2. Add Intelligence: Use AI actions to analyze and understand your data
  3. Take Action: Apply the appropriate record, communication, or file actions
  4. Monitor Results: Use the automation history to track performance
Ready to build your first automation? Return to the Automation System guide for step-by-step instructions and real-world examples.