# Introduction Welcome to the Lleverage documentation. Learn how to work with your AI coworker, build visual workflows, and monitor the automated processes that run your operations. ## What Lleverage does Lleverage automates repetitive back-office processes - order processing, invoice handling, quote generation, document workflows - with AI that works alongside your existing ERP and business systems. There are two ways to get work done: * **The Agent** - an AI coworker called Llev that you chat with. Give it tasks, upload files, and let it use your integrations, knowledge bases, and skills. New projects open on the agent by default. * **Workflows** - repeatable processes you build step by step on a visual canvas. The Workflow Copilot, which builds workflows from a plain-language description, is temporarily unavailable while it is being improved. {% @arcade/embed url="" flowId="2jNbdjXsZ1LBpQ7taSu9" %} ### How it works 1. **Ask the agent or build a workflow** - chat with Llev for day-to-day tasks, or use the visual canvas for structured processes that run the same way every time 2. **Keep people in control** - route approvals and exceptions to the Request Inbox so someone can review before work continues 3. **Publish and share** - deploy workflows as apps, API endpoints, or scheduled tasks 4. **Monitor and refine** - follow runs in Activity, keep an eye on your project Dashboard, and improve based on real results > πŸ’‘ Each project can open on the agent or use a workflow-focused sidebar instead. Choose the layout and the default landing page in Project Settings under **Navigation**. ### Key areas * [**The Agent**](/operator-agent/operator-agent) - your AI coworker: chat sessions, skills, files, and memory * [**Workflow Copilot**](/get-started/workflow-copilot) - describe a process in plain language and it builds the workflow for you (temporarily unavailable while it is being improved) * [**Tables**](/platform/data-tables) - structured business data your agent and workflows can read and update * [**Request Inbox**](/platform/request-inbox) - approvals and inputs that need a human, with assignment, notes, priorities, and SLAs * [**Activity Monitoring**](/platform/activity-monitoring) - run history and detail for everything that happens in your project * [**Knowledge Bases**](/platform/knowledge-bases) - searchable document collections that give the AI context about your business * [**Publishing**](/publishing-guide/publishing-workflows) - share workflows as apps, API endpoints, or schedules * [**Roles and Permissions**](/roles-and-permissions) - control who can build, run, and view * [**Security & Performance**](/technical/security-and-performance) - how Lleverage protects your data ### Getting help If you need assistance with a specific implementation or run into issues, reach out to your Lleverage contact or visit [Troubleshooting and Support](/support/troubleshooting-and-support). # Workflow Copilot > ⚠️ The Workflow Copilot is temporarily unavailable while it is being improved. The Copilot panel and its controls are hidden from the workflow canvas, and Copilot features such as workflow generation, Auto Fix, and guided template setup are switched off for now. You can still build and edit workflows manually on the canvas. This page is kept as a reference for when the Copilot returns. The Workflow Copilot is your intelligent assistant for creating and editing complete workflows using natural language. It works from a panel alongside the canvas. ### Copilot Capabilities The Copilot operates seamlessly across multiple interaction modes that automatically adapt based on your current context and needs: * **Generate**: Creates workflows from scratch on a blank canvas * **Edit**: Modifies existing workflows and individual actions with precision * **Chat**: Provides conversational explanations and discussions about workflows * **Fix and rerun**: Fixes errors and reruns workflows with existing criteria * **Smart Detection**: Auto-detects optimal placement for additions, edits, and refinements ### Getting Started with Copilot #### Creating Your First Workflow 1. **Access the Canvas**: Create a new workflow to reach the landing page 2. **Choose Your Starting Point**: * Select from suggested prompt templates above the text box (backed by real data) * Use the refresh button to see more template suggestions * Access the full template library for comprehensive options * Or start from scratch with your own description 3. **Describe Your Workflow**: * Be specific about integrations and data you want processed * Structure your text clearly and keep it concise * The more detailed and specific you are, the better results you'll get * Include specific values and parameters you want handled 4. **Submit and Generate**: Click the submit button to start generation #### Generation Process When you submit your prompt, you'll see the Copilot working in its panel: * Your original prompt appears first * Real-time progress updates show step-by-step generation * **Visual Distinction**: Copilot messages and actions have different UI styling to help you understand what's being processed * Clear completion messages guide you to next steps ### Copilot Permissions The Copilot asks before doing anything with side effects, and you can loosen this from the settings control in the Copilot panel: * **Auto Run**: Run workflows without asking. With this on, the Copilot can also fix errors and rerun the workflow automatically without checking with you each time. * **Auto Fill**: Fill forms automatically. The Copilot completes input forms for you when a run needs them. > πŸ’‘ Both permissions are off by default, so the Copilot will always ask before running your workflow or filling in a form until you switch them on. ### Reviewing Copilot Changes After the Copilot edits your workflow, it shows a change review so you stay in control: * Each change is labelled as **Added**, **Edited**, or **Deleted** * Expand any change to see the detail of exactly what was altered * Undo individual changes you don't want, without discarding the rest > ⚠️ Always review workflows after Copilot modifications, especially complex ones, before running or publishing them. ### Advanced Copilot Features #### Intelligent Clarification The Copilot will ask clarifying questions when needed to ensure your workflow meets your exact requirements. #### Connecting Apps When a workflow needs an app that isn't connected yet, the Copilot handles it inline: * If you have no connected account for that app, a **Connect** button appears so you can connect it on the spot * If you already have connected accounts, an account selector lets you pick which one the action should use #### Context-Aware Editing * **Select a node** to provide context for targeted editing * Give simple, natural instructions like "Simplify," "Fill it out," or "Fix it" * The Copilot edits the entire canvas while using your selected node as context #### Fixing and Rerunning When errors are detected, the Copilot can fix the issue and rerun your workflow with the same criteria, eliminating manual troubleshooting. If Auto Run is enabled, this happens without asking; otherwise the Copilot checks with you first. #### Auto-Generated Content * **Automated text and descriptions** for workflow components * **IO generation** for inputs and outputs * **Test generation** for workflow validation * **Prompt optimisation** handled automatically behind the scenes ### Working with Your Workflow #### Conversational Interaction Beyond editing, you can have natural conversations with your workflow: * Ask "What does this workflow do?" * Request explanations of specific functionality * Get suggestions for improvements #### Whole Canvas Editing Use the text box to describe changes you want across your entire workflow. The Copilot will modify the canvas comprehensively while maintaining functionality. #### Ripple Effect Management When the Copilot changes specific actions, it intelligently handles ripple effects throughout connected workflow components, ensuring everything remains functional. ### Best Practices for Optimal Results πŸ’‘ **Be Specific**: Include detailed information about integrations, data processing requirements, and specific values you want handled πŸ’‘ **Structure Clearly**: Keep prompts well-organised and concise rather than copying large text blocks πŸ’‘ **Use Context Selection**: Click on specific nodes before giving editing instructions to provide targeted context πŸ’‘ **Review Every Change**: Use the change review to expand, check, and undo individual changes before moving on πŸ’‘ **Tune Your Permissions**: Turn on Auto Run and Auto Fill once you're comfortable letting the Copilot run and fill things for you πŸ’‘ **Understand Ripple Effects**: Changes to one action may intelligently affect connected workflow components ### Key Advantages The Workflow Copilot transforms workflow creation from a technical task into a conversational experience. With intelligent auto-detection, automatic error fixing, and expert AI prompting built in, you can focus on describing what you want rather than how to build it. # FAQ Welcome to the Lleverage FAQ! Here you'll find answers to the most common questions about using the platform. If you don't see your question answered here, you can always reach out to support through the help menu in the app.
What is Lleverage? Lleverage is an AI automation platform for operational work. It pairs an AI coworker (the agent, called Llev) with visual workflows, so you can hand ad-hoc tasks to the agent and turn repeatable processes into step-by-step workflows that combine logic, AI, and system integrations - without needing developers.
What is the agent? The agent is an AI coworker called Llev that lives inside your project. You chat with it in natural language: give it tasks, upload files, and let it work with your connected apps, tables, and knowledge bases. It remembers context between sessions and can save repeatable ways of working as skills. New projects open on the agent by default.
What are skills? Skills are reusable task packages the agent can run - a saved way of doing a job, combining instructions, integrations, and knowledge. When the agent proposes a new skill, you review and approve it before it's saved, so you stay in control of how it works. You can also pick ready-made skills from the Skill Library instead of starting from scratch.
How do I get started with Lleverage? Open a new project and you'll land in a chat with Llev, your AI coworker - just describe what you need. If you'd rather build a workflow, open the visual canvas and build it step by step. The Workflow Copilot, which creates workflows from a description, is temporarily unavailable while it is being improved.
Is Lleverage secure? Yes, security is a core priority at Lleverage. We are SOC 2 Type 2 certified, GDPR compliant, and ISO 27001 certified. We implement enterprise-grade end-to-end security, secure authentication options, and API token management to ensure your data and workflows are protected.
Are my projects and workflows private? Yes, all your projects and workflows are private by default. Only people you explicitly invite to your organisation and projects can access them. You control who can view or edit your workflows through the permission system.
How do I create a workflow? To create a workflow, choose how it starts (a form, a chat, an API call, a schedule, or an integration event), then use the visual canvas to add actions, connect them together, and configure each step. The Copilot, which generates workflows from a natural-language description, is temporarily unavailable while it is being improved.
Can I connect Lleverage to other applications? Yes. Native integrations - including Gmail, Outlook, Slack, Microsoft Teams, SharePoint, Google Drive, and ERP systems such as Business Central and SAP S/4HANA - are connected in Settings under **Connections**, and thousands more apps are available through our app integrations. In the workflow editor, connected apps appear in the **Integrations** category when you add a step, and the agent can connect apps for you as part of a conversation. The Workflow Copilot, which can also connect apps, is temporarily unavailable while it is being improved.
Where do approvals and human input requests appear? In the Request Inbox. When the agent or a workflow needs a person to approve something or fill in missing information, a request appears there and the run pauses until it's handled. Requests can be assigned and reassigned, carry notes, and have priorities and SLAs, so the right person deals with the right thing on time.
How do I pass data between nodes in my workflow? Click on an input field where you want to use data from a previous step, then click the @ button in the field. This opens a picker where you can select the variable you need. For advanced users, you can also use the {{ }} method to access specific properties.
Can I test my workflow before publishing it? Yes, use the Run Panel in the workflow editor to test your workflow with sample inputs and see the results before publishing it for real use.
How do I fix errors in my workflow? Steps with configuration issues are highlighted on the canvas. Open the step to see which fields need attention, and check the validation messages in the editor for details about what's missing or misconfigured.
How do I set up a loop in my workflow? Add a **For Each** node from the Controls section when adding a step, connect your input data (typically a list), and add the actions to perform on each item inside the loop. The workflow processes each item in turn. There are also **Repeat** and **Do While** nodes for loops that run a set number of times or until a condition is met.
How do I publish my workflow? Click the **Publish** button in the workflow editor. The publish options depend on how your workflow starts - app links for forms and chats, or API endpoints for API call triggers.
How do I share my workflow with others? First, add the person to your organisation and to the specific project containing the workflow, with a role that matches what they need to do. Then you can share the published workflow URL with them.
Can I embed my Lleverage workflow in my website? Yes, for form and chat workflows you can embed your workflow in a website using the iframe code provided when you publish. This works with WordPress and other website platforms through custom HTML blocks.
How do I control who can access my workflows? Lleverage uses a permission system with roles at both organisation and project level. At the organisation level, the roles are Owner, Builder, Operator, and Member; at the project level, Project Admin and Project Member. See [Roles and Permissions](/roles-and-permissions) for what each role can do.
How do I stay on top of what my workflows are doing? The Activity page shows the run history for your project, and the notification bell in the sidebar collects updates that need your attention. Your project Dashboard also gives you an overview of how things are running.
Which AI models does Lleverage support? Lleverage provides a curated selection of state-of-the-art AI models from leading providers including OpenAI, Anthropic, Google, Together AI, and Mistral. The available models are kept up to date as providers release new ones.
How do I choose the right AI model for my workflow? Consider what the step needs to do. For simple, high-volume tasks, pick a faster, lighter model; for complex reasoning or nuanced writing, pick a more powerful one. You can test different models in the workflow editor and compare the results before settling on one.
Can I use my own API keys for AI models? Yes, you can add your own API keys in Settings under **AI Models**. This allows you to use your existing subscriptions with providers like OpenAI and Anthropic.
How do I set tokens for AI models? You can adjust token settings in the advanced settings of prompt steps. Open a prompt step, go to the Prompt Studio, then open the settings next to the model selection to find the advanced options, including tokens.
What should I do if my workflow isn't working as expected? Check for validation errors in the workflow editor, review the run details in Activity for information about what happened during execution, and use the Run Panel to test changes. If you're still having issues, contact our support team.
How do I report a bug or request a feature? Use the chat support in the help menu, or choose **Request Feature** from the user menu to send a suggestion to our product team.
Can I get help with building complex workflows? Yes, our support team can help with complex issues. You can also request a personalised demo at for guidance and to talk about building for specific use cases.
How do I set up environment variables or secrets? Go to Settings and open **Secrets** or **Variables**. Secrets securely store sensitive values like API keys and connection strings; variables hold reusable configuration values your workflows can reference.
Can I create a knowledge base from my documents? Yes, Lleverage allows you to create knowledge bases from documents, websites, and other text sources. Both the agent and your workflows can use them to give context-aware answers based on your own data.
Is it possible to schedule workflows to run automatically? Yes, you can use a schedule trigger to run workflows at predetermined times or intervals. This is ideal for recurring tasks like daily reports, periodic data processing, or routine system checks.
Can I connect to databases in my workflows? Yes, Lleverage provides database connection capabilities. You can connect to databases like MySQL and PostgreSQL to query and manipulate data as part of your workflows.
How can I monitor the performance of my workflows? Lleverage automatically logs all workflow executions. Open the Activity page to view detailed information about each run, including inputs, outputs, and execution times.
How do I get workflow outputs as CSV or other formats? You can configure your workflow to format the output as CSV or other formats using the appropriate formatting steps. For downloadable files, use actions that can deliver files via email or store them in connected storage services.
Can I connect my email account to workflows? Yes, you can connect email accounts like Gmail and Outlook to your workflows. This allows you to create automations that can read emails, send responses, or process email attachments.
# Key Terms Welcome to Workflow Automation! This guide explains common automation and AI terms in simple language to help beginners get started. ### Workflow A workflow is a series of connected steps that automate a task from start to finish. Think of it like a recipe that tells the system exactly what to do in what order. > πŸ’‘ Example: A workflow might automatically read emails, extract important information, and create a summary report. ### LLM (Large Language Model) An AI system trained on vast amounts of text that can understand and generate human-like language. LLMs power the AI capabilities in Lleverage. > πŸ’‘ These models can write content, answer questions, summarize information, and more based on your instructions. ### Prompt Instructions you give to an AI model telling it what you want it to do. The quality of your prompt determines the quality of the AI response. > ⚠️ Be specific in your prompts. "Write a professional email" will give generic results, while "Write a professional email declining a vendor proposal due to budget constraints" will give more targeted results. ### Agent An automated assistant that combines AI with specific functions to accomplish tasks. Agents can make decisions and take actions based on the instructions in your workflow. ### Trigger The starting point of a workflow that determines when and how it begins. Lleverage offers several trigger types: * **Form**: Collects information through fields you fill out * **Chat**: Starts a workflow through a conversation interface * **API Call**: Allows other applications to start your workflow * **Schedule**: Runs automatically at specific times * **Integration**: Activates when something happens in another application ### Knowledge Base A collection of documents and information that your AI can access and reference when answering questions or completing tasks. > πŸ’‘ Adding company policies to a knowledge base allows the AI to answer questions according to your specific guidelines. ### Run Testing your workflow in the builder to see how it performs before making it available to others. ### Publish Making your workflow available for use after you've built and tested it. Publishing creates a link, embed code, or API endpoint that others can use. ### External Apps Connections to other tools and services (like Gmail, Slack, or Salesforce) that your workflow can interact with. > πŸ’‘ External apps let your workflows send emails, post messages, update records, and more. ### Embedding Adding your workflow to a website or application so it can be used there. This is done using a special code provided when you publish your workflow. ### Variables Containers that store information within your workflow. Variables let different parts of your workflow share and use the same information. > πŸ’‘ Example: If a user enters their name in a form, that name is stored in a variable that can be used in later steps. ### Types of Applications You Can Build With Lleverage, even non-technical users can create: * **Content generators**: Create marketing materials, emails, or reports automatically * **Virtual assistants**: Build chatbots that answer questions using your company information * **Data processors**: Extract and organize information from documents or websites * **Approval systems**: Create workflows for reviewing and approving requests * **Notification systems**: Send alerts when important events happen # Tutorials Step-by-step guides for the most common things you'll do in Lleverage. While video tutorials are being prepared, these pages walk you through the same ground. ### Start here * [**The Agent**](/operator-agent/getting-started) - meet Llev, your AI coworker, and run your first task in chat * [**Workflow Copilot**](/get-started/workflow-copilot) - describe a process in plain language and let the Copilot build the workflow for you (temporarily unavailable while it is being improved) ### Build a workflow * [**Triggers**](/canvas-actions/triggers) - choose how your workflow starts: a form, a chat, an API call, a schedule, or an integration event * [**Action Cards**](/canvas-guide/action-cards) - add and configure the steps that do the work * [**Variables and Data Flow**](/canvas-guide/variables-and-data-flow) - pass data from one step to the next * [**Run Panel**](/canvas-guide/run-panel) - test your workflow with sample inputs before it goes live ### Go live * [**Publishing Workflows**](/publishing-guide/publishing-workflows) - share your workflow as an app, API endpoint, or schedule * [**Activity Monitoring**](/platform/activity-monitoring) - follow runs and dig into what happened # Operator Agent The Operator Agent is your AI coworker inside Lleverage - chat with it, give it tasks, upload files, and let it work with your integrations, knowledge bases, and skills to get things done. The Operator Agent is an AI coworker that lives inside your Lleverage project. In the product it appears as **Llev** by default - though its name, instructions, and tone can all be configured per project. Rather than building a workflow step by step, you talk to the agent in natural language: describe what you need, and it figures out how to get it done using the tools and data available in your project. ### What the Agent Does The Operator Agent can: * **Process files** β€” Upload CSVs, PDFs, images, spreadsheets, and other documents. The agent reads, analyses, and transforms them in a secure cloud sandbox. * **Use your integrations** β€” Connected apps (Gmail, Slack, Business Central, etc.) become tools the agent can use on your behalf. * **Query knowledge bases** β€” The agent searches your uploaded documents and knowledge bases to find relevant information. * **Run skills and workflows** - Skills are reusable task packages that combine instructions, integrations, and knowledge; the agent can also run your existing workflows as part of a task. * **Generate output files** - The agent can create documents, spreadsheets, reports, and other files as part of its work, and save them to your project files or a knowledge base. * **Ask for your input** - When the agent needs a decision, an answer, or a file, it raises a request in the session, which also appears on your project's Requests page. * **Break down complex tasks** β€” For larger requests, the agent plans its approach, tracks progress with a visible todo list, and narrates what it's doing in real time. ### Your Agent, Your Way The agent is configurable per project: * **Name** - The agent takes the project name as its own, so each project's agent has its own identity. * **Instructions** - Project instructions describe what the project is about and guide the agent at the start of every session. * **Tone** - Choose how the agent sounds in replies: Crisp, Balanced, or Warm. * **Memory** - The agent builds up a project memory over time, so what it learns in one session carries over to the next. ### Agent vs. Workflows Workflows and the agent serve different purposes: | | Workflows | Operator Agent | | ----------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------ | | **Best for** | Repeatable, structured processes that run the same way every time | Ad-hoc tasks, exploration, complex reasoning | | **How you build** | Visual canvas with connected action cards | Natural language conversation | | **Execution** | Deterministic β€” follows the path you designed | Autonomous β€” decides its own approach | | **Triggers** | Schedules, API calls, form submissions, integrations | Chat, schedules, messaging channels (Slack and Microsoft Teams), and workflows | | **Monitoring** | Activity log, run history, alerts | Session history, narration, progress panel | Many teams use both: workflows for high-volume automated processes, and the agent for tasks that need judgement, flexibility, or one-off analysis. ### Getting Started Open your project and go to the agent to start a conversation. {% content-ref url="/pages/QBgYQ0dlrJa7h7B4EJN3" %} [Getting Started](/operator-agent/getting-started) {% endcontent-ref %} # Getting Started Open the agent, explore its home screen, configure how it behaves, and see it work through your first task in real time. The Operator Agent is accessible from the main navigation inside any project. Open the agent section to land on its home screen, where you can start a conversation or pick up a suggested task. ### The Agent Home Screen Before you start a session, the home screen offers a few ways in: * **Suggestion cards** - Cards suggesting tasks the agent can help with, tailored to your project. Pick one to start a session with that task, or ignore them and type your own message. * **Attention cards** - If the agent is waiting on you - for example a pending approval or an unanswered question from an earlier session - a card appears so you can respond without hunting for the right conversation. * **Onboarding cards** - When a project is new, checklist cards walk you through introducing yourself, connecting your tools, and giving the agent its first task. Builders can shape this screen for the whole team: 1. **Open the card editor** from the agent home screen. 2. **Drag cards to reorder** them, edit a card's content, or hide individual cards. 3. **Toggle whole sections** - hide the entire cards section or switch suggestions off altogether. ### Configuring Your Agent The agent's identity and behaviour are set per project: * **Name** - The project name is also the agent's name. By default the agent is called Llev. * **Project instructions** - A description of what the project is about, given to the agent at the start of every session. Use it for standing guidance: what the team does, preferences, things to always or never do. * **Agent tone** - How the agent sounds in replies: Crisp, Balanced, or Warm. * **Organisation branding** - Optionally show your organisation's logo on the agent's home screen. > πŸ’‘ Instructions and tone apply to every session in the project, so everyone on the team gets a consistently behaving agent. ### Your First Conversation 1. **Type a message** in the composer at the bottom of the screen. Describe what you need β€” for example: *"Summarise the key figures from this quarterly report"* or *"Draft an email to the supplier about the delayed shipment."* 2. **Hit send.** The agent begins working immediately. 3. **Watch it work.** The agent narrates what it's doing in real time - you'll see status messages describing each step, plus skill and tool cards appearing as they're invoked. 4. **Keep typing if you like.** You can send follow-up messages while the agent is still working - they queue up and are handled in turn - or stop the agent mid-task if it's heading the wrong way. ### Uploading Files You can upload files by: * **Dragging and dropping** files directly into the chat * **Using the attach button** in the composer Supported file types include: * **Documents** β€” PDF, Word (.docx), PowerPoint (.pptx) * **Spreadsheets** β€” CSV, Excel (.xlsx) * **Images** β€” PNG, JPG, and other common formats * **Email files** β€” EML * **Other text formats** β€” JSON, XML, plain text The agent processes uploaded files in a secure cloud sandbox. It can read PDFs visually (not just as extracted text), parse spreadsheets, and extract data from images. ### Understanding the Interface While the agent is working, you'll see several elements: * **Narration** - Short status messages describing what the agent is currently doing. * **Skill and tool cards** - When the agent uses a skill or an integration, a card appears showing its name and progress. Cards appear immediately in a loading state and update in place as they complete. * **Request cards** - When the agent needs something from you - an approval, an answer, or a file - a card appears in the chat for you to respond to. * **The right panel** - A side panel showing the agent's progress on longer tasks, generated files, the context it's using, and its memory. ### Tips for Your First Session * **Be specific.** The more context you give, the better the result. Instead of *"Process this file"*, try *"Extract all order line items from this PDF and create a CSV with columns for SKU, quantity, and unit price."* * **Upload files with your message.** The agent works best when it has the data it needs upfront. * **Follow up naturally.** You can ask the agent to refine, adjust, or build on its previous output within the same session. * **Check the narration.** If the agent seems stuck or headed in the wrong direction, the narration shows you what it's doing so you can redirect it. # Chat & Sessions Each conversation with the agent is a session. Sessions can start from chat, schedules, messaging channels, or workflows - and you can manage them all from the Agent Sessions page. Every conversation with the Operator Agent is a **session** (also called a thread). A session preserves the full context of that conversation - messages, uploaded files, generated outputs, and the agent's working notes. ### How Sessions Start Sessions don't only begin when you type a message. A session can start from: * **Chat** - You open the agent and send a message. * **A schedule** - The agent runs a task on a recurring schedule and records the run as a session. * **A messaging channel** - Messages from connected channels such as Slack or Microsoft Teams start and continue sessions. * **A workflow** - Workflows can hand tasks to the agent, which run as sessions too. You can start a new session at any time from the agent home screen, continue an existing one from the session list, and run multiple sessions in parallel for different topics. ### The Composer The message box does more than plain text: * **Mentions** - Type `@` to reference a workflow or data table, or `/` to reference a skill, directly in your message. The agent then knows exactly which resource you mean. * **The + menu** - Attach resources to the conversation from four panels: Skill, Workflow, Data table, and Connections. * **Voice input** - Dictate your message instead of typing it. * **Queued messages** - Send follow-ups while the agent is still working; they queue up and are handled in turn. You can remove a queued message before it's picked up. * **Stop** - Stop the agent mid-response if it's heading the wrong way, then redirect it. ### Choosing a Model A settings control in the chat lets you choose how the agent thinks for the current session: * **Auto** - Lets the platform route each request to a suitable model automatically. * **A specific model** - Pick an exact model if you have a preference. * **Thinking** - For models that support it, choose how much reasoning effort the agent puts in. > πŸ’‘ Model settings apply per session, so you can use a fast model for quick questions and a more thorough one for complex work. ### The Right Panel Alongside the chat, a panel keeps track of the session: * **Progress** - The agent's todo list for longer tasks, ticked off as it works. * **Files** - Files generated or used during the session. * **Context** - The skills, connections, and other resources the agent is drawing on. Selecting a skill opens it for review and editing without leaving the chat. * **Memory** - What the agent has learned and remembered for this project. ### Requests from the Agent When the agent needs something from you mid-task - approval to proceed, an answer to a question, or a file - it raises a **request**. The request appears as a card in the session, and also on your project's Requests page, so nothing gets missed even if you've moved on. Respond from either place and the agent carries on. ### Chatting from Slack and Teams You can connect messaging channels so the agent is available where your team already works. Once a channel is connected, you can chat with the agent directly inside Slack or Microsoft Teams, and those conversations appear as sessions in Lleverage. ### Managing Sessions The sidebar shows your recent sessions for quick access. For the full picture, open the **Agent Sessions** page, where you can: * **Search and filter** sessions - for example by status, such as those needing attention, active, or completed * **Favourite** sessions you want to keep close to hand * **Rename** sessions so they're easy to find later * **Archive and unarchive** sessions to keep the list tidy without losing anything * **Delete** sessions you no longer need, individually or in bulk ### Session Privacy Sessions are scoped to your user account. Other users in the same project cannot see your sessions, and you cannot see theirs. ### Context Within and Across Sessions Within a session, the agent remembers everything - previous messages, file uploads, skill results, and generated outputs. You can refer back naturally: * *"Use the same format as the report you generated earlier"* * *"Now do the same thing for the second file I uploaded"* * *"Actually, change the date column to DD/MM/YYYY"* For very long sessions, the agent manages its context window automatically to stay within model limits. Across sessions, the agent isn't starting from scratch either: project instructions, tone, and the project's memory carry over, so the agent keeps what it has learned about your team and how you like to work. Open a new session when you want a clean conversation for a new topic - the conversation itself starts fresh, but the agent's knowledge of your project comes with it. # Skills Skills are reusable capabilities that extend what the agent can do, bundling instructions, connections, workflows, knowledge, data, and files into repeatable tasks. Skills are the building blocks that make the Operator Agent useful for your specific business processes. A skill packages up everything the agent needs to perform a particular task: instructions on what to do, connections to external systems, and access to relevant knowledge and data. ### What Is a Skill? Think of a skill like an app for your agent. Just as you install apps on your phone to add capabilities, you add skills to your project to teach the agent new tasks. A skill can include: * **Instructions**: what the agent should do when the skill is used, how it should behave, and what output to produce. * **Connections**: connected apps (e.g. Gmail, Business Central, Slack) with the accounts needed to use them. An account can be shared by everyone, or each operator can connect their own. * **Workflows**: existing workflows from your project that the skill can run as part of its work. * **Knowledge bases**: document collections the agent can search for context and reference data. * **Data tables**: structured data the agent can query and update during execution. * **Files**: reference documents bundled with the skill, such as templates or examples. You can view and edit them from the skill page. Each skill also has a name, a description, and an icon so it is easy to recognise across the product. ### Where Skills Come From * **Create your own**: build a skill on the Skills page, or ask the agent to create one during a chat. The agent proposes the skill and nothing is saved until you approve it. * **Install from the Skill Library**: browse ready-made skills built by Lleverage and install them into your project. Installed skills become project skills you can adapt like any other. ### How Skills Work at Runtime When you give the agent a task, it evaluates which of its available skills are relevant and loads them as needed. When a skill loads, the agent reads its instructions and carries on following them in the same turn, so there is no pause between picking the skill and doing the work. You can also invoke a skill yourself, either explicitly in the message box or from the Explore page. The agent can: * Use **multiple skills** in a single session * Decide **which skills to use** based on your request * **Chain skills together** when a task requires several capabilities ### Skill Visibility What you can do with skills depends on your project role. Project roles are Owner, Builder, Operator, and Member: | Role | What you can do | | --------------------- | -------------------------------------------------------------------------------- | | **Owner / Builder** | Create, edit, test, and publish skills, including drafts and version history | | **Operator / Member** | Use skills through the agent. The agent only ever runs published, enabled skills | {% content-ref url="/pages/w8GlWwXaO54V8gcV2up8" %} [Using Skills](/operator-agent/skills/using-skills) {% endcontent-ref %} {% content-ref url="/pages/HU86KkoN2CJcfOizUE0N" %} [Creating Skills](/operator-agent/skills/creating-skills) {% endcontent-ref %} # Using Skills Browse your project's skills, install ready-made ones from the Skill Library, and run them in agent sessions. The Skills page shows every skill in your project, and the Skill Library lets you add ready-made ones built by Lleverage. This page covers finding skills, turning them on and off, and running them in a session. ### Browsing Skills The Skills page lists all skills in your project. Each skill card shows: * **Name, icon, and description**: what the skill does * **Badges**: a **Draft** badge when the skill has unpublished changes, and a **Disabled** badge when it is switched off * **Actions**: **Use** starts an agent session with the skill; owners and builders also see **Test** on skills with a draft You can search skills and switch between a grid view and a list view. ### The Skill Library The Skill Library contains ready-made skills built by Lleverage that you can install into your project: 1. **Open the library**: click **Library** on the Skills page. The library is also offered as a card on the agent's home screen. 2. **Browse or search** the available skills to find ones relevant to your work. 3. **Install**: click **Install skill**. If the skill uses a connected app, you choose which account it should use: a **shared account** that everyone uses, or a **personal account** where each operator connects their own. Installed skills become normal project skills: you can adapt their instructions and components just like a skill you created yourself. > πŸ’‘ Installing a skill publishes it into your project straight away, so the agent can use it immediately. ### Enabling and Disabling Skills Owners and builders can toggle skills on or off per project: * **Enabling** a skill makes it immediately available to the agent, so it can be used in any session. * **Disabling** a skill removes it from the agent's tool context. The agent can no longer use it, but the skill is not deleted and can be re-enabled at any time. This is useful when: * A skill is causing the agent to select it when it shouldn't * You want to temporarily remove a capability without losing the skill configuration * You're testing a new skill and want to limit its availability > ⚠️ Disabling a skill takes effect immediately. Any active sessions where the agent was about to use that skill will no longer have access to it. ### How the Agent Chooses Skills You don't need to tell the agent which skill to use. When you describe a task, the agent evaluates its available skills and selects the most relevant ones automatically. For example, if you say *"Process the incoming order from this email"* and you have an order processing skill enabled, the agent will recognise the match and use it. ### Invoking a Skill Yourself You don't have to wait for the agent to pick a skill: * **In the message box**: type **/** and choose the skill from the list. It appears in your message as a reference, and the agent loads that skill when you send it. * **From the Skills page**: click **Use** on a skill card to start a session with it. * **From the Explore page**: the agent's Explore page lists your skills alongside suggested prompts and apps. Choosing a skill starts a session with it. > πŸ’‘ You can bring a skill in mid-conversation too. Reference it at any point and the agent loads the skill's instructions and follows them in the same turn. ### Skills in the Chat When the agent loads a skill, you'll see it in the chat stream, so it is always clear which skill is being used. As the agent works through the skill, you can follow its progress and the tools it calls. Clicking a skill opens its detail panel beside the chat, showing the skill's instructions and components. Owners and builders can edit the skill from there without leaving the conversation. # Creating Skills Author skills for the agent: write instructions, add components, review the agent's proposed changes, and manage drafts and versions. Skills are created by owners and builders. You can build one yourself from the Skills page, or ask the agent to create one during a chat session and approve its proposal. ### Creating a Skill from the Skills Page 1. **Open the Skills page** in your project and click **New**. 2. **Give the skill a name** that describes the task (e.g. "Order Processing", "Quote Generation"). 3. **Pick an icon**: choose an emoji or upload an image so the skill is easy to spot. 4. **Write the instructions**: the core of the skill. Tell the agent what to do, how to behave, and what output to produce. 5. **Add a description** of what the skill does. If you leave it empty, one is generated for you when you leave the page. Your changes save automatically as a draft while you work. ### Creating a Skill from Agent Chat You can also ask the agent to create or change a skill during a conversation. For example: * *"Create a skill that processes incoming purchase orders from email attachments"* * *"Turn what you just did into a reusable skill"* The agent never saves anything itself. Instead it proposes the change and asks for your approval: 1. **A review card appears in the chat** summarising what the agent wants to do. 2. **Open the full review in the side panel** to see exactly what would change, including a preview of the version that would be created or published. 3. **Approve or cancel**. Depending on the proposal, the approve button reads **Create draft**, **Create Skill**, **Save changes**, **Publish changes**, **Discard draft**, or **Revert**. Choose **Cancel** and nothing changes. > ⚠️ The agent can propose creating, updating, publishing, discarding, reverting, or deleting a skill, but none of it happens until you approve it in the review. ### Adding Components Once a skill exists, add components that give it access to systems and data. Open the **Add Component** dialog on the skill page and pick a tab: * **Workflows**: let the skill run an existing workflow from your project. You can require approval before the workflow runs. * **Files**: upload reference documents such as templates or examples. You can view and edit a file's content from the skill page. * **Connections**: connect apps the skill needs (e.g. Gmail, Business Central, Slack). Decide which account the skill uses when operators run it: a **shared account** that everyone uses, or a **personal account** where each operator connects their own before using the skill. * **Data Tables**: structured data the agent can read from or write to. You can require approval before the skill writes to a table. * **Knowledge Bases**: document collections the skill can search. Useful for skills that need reference data such as product catalogues, pricing rules, policy documents, or technical manuals. ### Drafts, Publishing, and Versions A skill can have a draft alongside its published version, so you can work on changes without affecting what operators use: * **Drafts**: editing a skill creates or updates its draft while the published version keeps running unchanged. Skills with unpublished changes show a **Draft** badge. * **Testing**: owners and builders can **Test** a draft in an agent session before publishing it, even when a published version already exists. * **Publishing**: publish the draft to make the changes live. A skill needs a description and instructions before it can be published, and each publish creates a new version. * **Discarding**: throw the draft away and keep the published version as it is. Discarded changes cannot be recovered. * **Reverting**: go back to an earlier published version. The selected version replaces the current draft, and you publish it to make it live. Skills keep a version history, so you can see what changed and when, and revert to an earlier version if needed. > πŸ’‘ The agent only ever runs published, enabled skills. Draft changes are never used in operators' sessions until you publish them. ### Editing a Skill During a Chat Session You can adjust a skill without leaving a conversation: * **Open the skill's panel**: click the skill in the chat to open its detail panel beside the conversation. Owners and builders can edit the instructions and components there directly. * **Ask the agent**: describe the change you want, then approve the agent's proposal from the review card. ### Managing Skills From a skill's page, you can: * **Edit** the skill's name, icon, description, instructions, and components * **Enable / disable** the skill for the current project * **View version history** and revert to an earlier version * **Delete** the skill if it's no longer needed # File Handling Upload documents, spreadsheets, images, and other files for the agent to process. The agent reads, transforms, and generates files in a secure cloud sandbox. The Operator Agent can work with files throughout a conversation β€” reading uploads you provide, processing data, and generating new files as output. ### Uploading Files Upload files by dragging and dropping into the chat, or using the attach button in the composer. You can upload files alongside a message to give the agent immediate context. #### Supported File Types | Type | Formats | | ---------------- | ------------------------------------- | | **Documents** | PDF, Word (.docx), PowerPoint (.pptx) | | **Spreadsheets** | CSV, Excel (.xlsx) | | **Images** | PNG, JPG, and other common formats | | **Email** | EML | | **Data** | JSON, XML | | **Text** | Plain text (.txt), Markdown (.md) | ### How the Agent Processes Files Uploaded files are processed in a **secure cloud sandbox** β€” an isolated environment where the agent can safely read, transform, and generate files without affecting your local system or other users. The agent handles different file types intelligently: * **PDFs** β€” The agent can read PDFs visually, preserving layout and formatting context. For large PDFs, it works with specific page ranges rather than processing the entire document. OCR is available for scanned documents. * **Images** β€” Processed as native visual content, so the agent can describe, analyse, or extract information from images directly. * **Spreadsheets and CSVs** β€” Parsed into structured data that the agent can query, filter, transform, and export. * **Office documents** β€” Word and PowerPoint files are converted to structured text, with the ability to extract embedded images. ### Generated Files and Artefacts When the agent creates files as part of its work - reports, transformed spreadsheets, exported data - these appear as **artefacts** in the session, collected in the Files section of the right panel. For each artefact you can: * **Preview** the generated content * **Download** the file * **Save to Files** - keep it in your project's files so it outlives the session * **Save to Knowledge Base** - add it to a knowledge base so the agent can find and reference it in future sessions Common output formats include CSV, Excel, PDF, and plain text, depending on what you asked for. > πŸ’‘ File names are preserved where possible. If the agent generates multiple files, each appears as a separate artefact. ### Requesting Files from You The agent can also ask for files. If a task needs a document you haven't uploaded yet, the agent raises a request in the session - respond by uploading the file and it continues from there. ### Sandbox Environment The cloud sandbox comes pre-loaded with common tools and libraries for file processing: * Python with data processing libraries * PDF tools (extraction, rendering, OCR) * Image processing capabilities * Document conversion utilities This means the agent can handle complex file operations β€” merging spreadsheets, extracting tables from PDFs, converting between formats β€” without requiring you to install anything. ### Tips for Working with Files * **Upload files with your first message** so the agent has context from the start. * **Be specific about what you want** β€” *"Extract the table on page 3"* works better than *"Look at this PDF."* * **For large files**, tell the agent which parts matter β€” specific pages, columns, or sections. * **Check the Files section of the right panel** for generated outputs - they may contain more detail than the chat summary. * **Save anything worth keeping.** Save important outputs to your project files or a knowledge base rather than leaving them in the session. # Integrations Connect external apps so the agent can use them as tools β€” send emails, update records, query systems, and more. The Operator Agent can interact with external systems through connected integrations. Once an app is connected, the agent can use its actions as tools β€” reading data, sending messages, updating records, and more. ### How Integrations Work with the Agent The agent draws on connections from two places: * **Project connections** - Apps connected to the project are available to the agent directly in chat. You can see and manage them from the Connections panel in the composer's + menu. * **Skill connections** - Skills can bundle their own integration credentials, so a skill always runs with the accounts it was built with. For example: * **Gmail** β€” Read emails, send replies, search for messages * **Business Central** β€” Look up orders, update records, create entries * **Slack** β€” Send messages, post to channels * **Google Sheets** β€” Read and write spreadsheet data * **Salesforce** β€” Query and update CRM records The agent decides when and how to use these integrations based on your request. You don't need to specify which integration to use β€” the agent matches your task to the available tools. ### Managing Connections in Chat The Connections panel in the composer's + menu shows the apps available to the agent in the current conversation: 1. **Open the + menu** in the composer and choose Connections. 2. **Toggle apps on or off** for this conversation - switched-off apps won't be used by the agent until you switch them back on. The toggles are per conversation, so a new session starts with everything enabled. 3. **Connect a new account** from the same panel if the app you need isn't listed. > πŸ’‘ The agent can also offer to connect an app mid-conversation. If your message mentions an app that isn't connected yet, the agent can walk you through authorising it right there in the chat. ### Connecting Through Skills Skills can carry their own integrations: 1. Open the skill that needs the integration 2. Add the integration app as a component 3. Connect your account when prompted Credentials attached to a skill are scoped to that skill - the agent uses them when running the skill, and won't borrow them for unrelated work. > ⚠️ Each integration connection requires authentication with the external service. Make sure you have the right permissions in the target system. ### Available Integrations Lleverage supports a wide range of integration apps. See the [External Apps Integration](/external-apps-integration) section for the full list of supported apps and their configuration details. ### Integration Actions in Chat When the agent uses an integration during a session, you'll see it reflected in the chat: * **Tool cards** show which integration action is being called * **Narration** describes what the agent is doing with the integration * **Results** are summarised in the agent's response This gives you visibility into exactly how the agent is interacting with your external systems. ### Security and Credentials * The agent only uses connections that are available to it - project connections you've enabled for the conversation, and credentials explicitly attached to its skills. * Integration connections use **OAuth or API key authentication** depending on the service. * Credentials are managed through the platform's secure credential store. * See [Secrets and Global Variables](/secrets-and-global-variables) for more on credential management. # Knowledge Bases Give the agent access to your documents and reference data through knowledge bases β€” it searches and retrieves relevant information automatically. Knowledge bases let the agent search through your uploaded documents and reference materials to find relevant information. Whether it's product catalogues, policy documents, technical manuals, or historical data β€” if it's in a knowledge base, the agent can find and use it. ### How the Agent Uses Knowledge Bases When a knowledge base is available (either directly in the project or through a skill), the agent can query it using vector search. This means: * The agent searches by **meaning**, not just keywords β€” asking about "delivery timelines" will find content about "shipping schedules" even if those exact words aren't used. * Results are **ranked by relevance** and the agent uses the most relevant content to inform its response. * The agent **cites its sources** so you can verify where information came from. ### Adding Knowledge to the Agent There are a few ways to grow what the agent can look up: * **Project knowledge bases** - Knowledge bases in your project are available to the agent in chat. * **Through skills** - Add a knowledge base as a component of a skill, so the skill always has its reference material to hand. * **From the agent's own output** - When the agent generates a useful file in a session, you can save it straight to a knowledge base so it's findable in future sessions. For details on creating and managing knowledge bases themselves, see [Knowledge Bases](/platform/knowledge-bases) in the Platform section. ### What to Put in a Knowledge Base Knowledge bases work best with: * **Reference documents** β€” Product specs, pricing lists, policy documents, SOPs * **Historical data** β€” Past orders, reports, templates * **Domain knowledge** β€” Industry standards, regulatory requirements, technical manuals * **FAQs and guides** β€” Common questions and their answers #### Supported Document Types * PDF (including scanned documents with OCR) * Word documents (.docx) * Spreadsheets (CSV, .xlsx) * JSON, XML * HTML * Plain text ### Knowledge Bases in Skills A skill can include one or more knowledge bases as components. This is useful because: * The knowledge base is **scoped to the skill's purpose** β€” the agent queries it in the right context * You can **version and manage** knowledge alongside the skill's instructions * Different skills can use **different knowledge bases** for different tasks For example, an order processing skill might include a product catalogue knowledge base, while a customer support skill might include a FAQ knowledge base. ### Tips * **Keep knowledge bases focused.** A smaller, relevant knowledge base performs better than a large, general one. * **Update regularly.** If your reference data changes (new pricing, updated policies), update the knowledge base so the agent has current information. * **Use descriptive document names.** This helps both you and the agent understand what's in the knowledge base. * **Feed good outputs back in.** Saving the agent's best reports and summaries to a knowledge base builds a growing library it can draw on. # Memory The agent builds a long-term memory of your project - facts, preferences, and knowledge it learns from sessions and files - so it carries context between conversations and gets more useful over time. Memory is what lets the agent learn. As it works through sessions, reads files, and receives feedback, the agent stores what it learns as memory - and reads it back in later sessions. That means it carries context between conversations: tell it something once, and it remembers next time. Memory is available on selected plans. ### How Memory Works During a session, the agent reads, writes, and searches its memory automatically. You don't need to manage this - it happens as part of the agent's normal work. Memory matures through three layers: * **Observations** - Raw and of-the-moment. Past sessions, reflections, and ingested files. * **Memories** - Distilled and reusable. Facts, preferences, and rules of thumb. * **Knowledge** - Settled reference. Curated articles, skills, and rules. New information enters at the bottom as observations, gets distilled into reusable memories, and can eventually settle into curated knowledge the agent treats as authoritative reference. ### The Memory Explorer Open **Intelligence > Memory** in your project to see everything the agent knows. The page shows memory as a layered map - three stacked planes, one per layer, with each document as a node. Related memories cluster together, and lines connect memories to the sessions and files they came from, so you can trace where any piece of knowledge originated. The map is live: when the agent stores or updates something during a session, the map refreshes on its own. To find something specific: 1. **Use the search field** in the side panel to search across all of memory. 2. **Select a result** to open the document and see exactly what the agent has stored. 3. **Click any node on the map** to preview that document in place. You can zoom, rotate, and reset the view using the on-screen controls, and the whole map can be navigated with the keyboard. Summary counts show how much sits in each layer. ### Reading and Editing Memory Anyone with access to the page can read memory documents. Each document shows its content alongside its layer, its type (for example a fact, preference, reference, or article), and when it was last updated. Users with the Builder role can also change what the agent knows: 1. **Open a document** from the map or a search result. 2. **Select the edit control** to switch the document into editing mode. Documents are plain markdown. 3. **Make your changes**, then choose **Save** - or **Discard changes** to leave the document as it was. Builders can also delete documents the agent should no longer rely on. > πŸ’‘ Editing memory directly changes how the agent behaves. If it has remembered something wrongly - an outdated fact, a preference that's changed - correcting the document here fixes it for every future session. > ⚠️ Deleting a memory removes it from what the agent knows. If you only want to correct a detail, edit the document instead. ### Seeding Memory in a New Project When a project has no memory yet, the Memory page helps you give the agent a head start. You can: 1. **Run a background check** - the agent researches your company and stores what it finds. 2. **Connect tools** - link the apps you work in so the agent can learn from them. 3. **Upload files** - share documents, decks, or notes for the agent to learn from. As each step completes, you'll see the first memories appear on a live map. You only need one of these to get going - the agent keeps learning from every session after that. ### Memory in Chat While you chat with the agent, a **Memory** card in the sidebar shows a miniature version of the memory map. When the agent stores something new mid-session, the card animates - zooming in on the new memory so you can see the moment it learns. Select a layer to list its documents, open any of them to read what was stored, or follow the link to the full Memory page. > πŸ’‘ The more the agent knows, the more useful it is. Mention your preferences, correct it when it gets something wrong, and give it feedback - all of that becomes memory it applies in future sessions. # Tips & Best Practices Get the most out of the Operator Agent β€” effective prompting, reading the agent's output, and knowing when to use the agent vs. a workflow. ### Writing Effective Prompts The agent responds to natural language, but how you phrase your request makes a real difference. **Be specific about the task:** | Instead of... | Try... | | ------------------- | ------------------------------------------------------------------------------------------------------ | | "Process this file" | "Extract all line items from this PDF and create a CSV with columns for SKU, quantity, and unit price" | | "Check this email" | "Read this email and draft a reply confirming we can deliver by the requested date" | | "Analyse this data" | "Compare Q1 and Q2 revenue by product category and highlight anything that changed by more than 10%" | **Provide context upfront:** * Upload all relevant files with your first message * Mention which systems or data sources are involved - or reference a skill, workflow, or data table directly in your message * Specify the output format you want (CSV, email draft, summary, etc.) **Iterate naturally:** The agent remembers everything in the current session. You can: * Ask it to revise: *"Change the date format to DD/MM/YYYY"* * Build on previous work: *"Now do the same for the March data"* * Redirect: *"Actually, focus on the top 10 by revenue instead"* **Teach it once:** The agent keeps a project memory, and project instructions apply to every session. If you find yourself repeating the same preference - a date format, a report structure, a tone - put it in the project instructions or tell the agent to remember it, and you won't have to say it again. ### Understanding the Agent's Output #### Narration While working, the agent shows short status messages describing each step. This is useful for: * **Knowing it's still working** on longer tasks * **Catching mistakes early** - if the narration shows it's headed in the wrong direction, you can stop it and redirect * **Understanding the approach** the agent took, which helps you refine future requests #### Progress For complex tasks, the agent keeps a todo list showing its plan, visible in the right panel. Items are checked off as they're completed, giving you a clear picture of progress. #### Skill Cards When the agent invokes a skill, a card appears in the chat. Skill cards show: * The skill name * Execution progress * Results when complete Cards appear immediately in a loading state and update in place β€” nothing shifts around or disappears. #### Requests When the agent needs your input, it raises a request - an approval, a question, or a file to provide. Answer it in the chat, or from your project's Requests page if you've moved on. ### When to Use the Agent vs. a Workflow **Use the agent when:** * The task is **ad-hoc or one-off** β€” you won't repeat it the same way every time * The task needs **judgement or reasoning** β€” interpreting documents, drafting responses, comparing data * You want to **explore or investigate** β€” "What's in this file?", "How does this compare to last month?" * The task involves **multiple steps that depend on what's found** β€” the agent adapts as it goes **Use a workflow when:** * The process is **repeatable and structured** β€” it runs the same way every time * **Volume is high** β€” processing hundreds of orders, invoices, or documents per day * You need **deterministic, auditable results** β€” every run follows the exact same logic > πŸ’‘ Scheduling and triggering aren't the deciding factor - agent sessions can start from schedules and messaging channels too. The real question is whether the task needs judgement (agent) or an identical result every time (workflow). **Use both together:** * Use the agent to **prototype and test** a process, then convert it to a workflow once it's proven * Use workflows for the **high-volume automation** and the agent for **exception handling and edge cases** * Use skills to **bridge the gap** β€” a skill created in the agent can encode a process that runs reliably every time ### Common Pitfalls * **Being too vague.** The agent will try its best, but vague instructions lead to generic results. Specificity wins. * **Not uploading files upfront.** If the agent needs data, give it the data in your first message rather than making it ask. * **Expecting workflow-level determinism.** The agent makes decisions β€” it might take a different approach to the same task on a different day. If you need consistency, use a workflow. * **Ignoring the narration.** The narration tells you what the agent is doing. If it's going wrong, catch it early and redirect. * **Leaving requests unanswered.** If the agent has asked for an approval, an answer, or a file, it's waiting on you - check the chat or the Requests page. # Project Dashboard The project dashboard is the customisable home page of a project. It combines stat tiles, charts, and ready-made components in a flexible grid, so each project can surface exactly what its team needs. Builders design the dashboard, including a separate layout for the operators who run workflows day to day. ### Key Features * Stat tiles giving quick counts and entry points for the main areas of the project * A drag-and-drop grid of widgets, with rows of up to four columns * Charts and stats built from your project's own data, with filters, scoping, and targets * AI-generated widgets and AI commentary on your data * Ready-made standard components such as recent items, quick links, and text blocks * Separate layouts for builders and operators ### Builder View and Operator View The dashboard has two layouts: * **Builder View**: the layout builders see, geared towards building and monitoring. * **Operator View**: a separate layout shown to operators and members when they open the project. Builders can switch between the two with the view menu in the dashboard header. Editing while in Operator View changes what operators will see, so you can design a focused home page for the people who run your workflows without exposing builder tools. > πŸ’‘ Dashboard layouts are shared across the project. Everyone sees the same layout for their view, rather than a personal arrangement. ### How to Edit the Dashboard 1. **Open edit mode**: click the pencil button in the dashboard header (builders only). 2. **Make your changes**: add, move, resize, or remove tiles and widgets. 3. **Keep your changes**: click the tick button (Done). 4. **Or discard them**: click the cross button (Discard changes) to revert everything since you started editing. ### Stat Tiles A row of tiles at the top of the dashboard gives quick counts and shortcuts for **Workflows**, **Apps**, **Knowledge**, **Tables**, **Requests**, and **Agent**. * In edit mode, remove a tile with its minus button. Removed tiles show as dashed placeholders you can click to bring back. * Drag tiles to reorder them. * Some tiles only appear when the related feature is available in your project, and the Knowledge tile is not shown in Operator View. ### The Widget Grid Widgets sit in a grid made of rows, each holding up to four columns: * **Add a row**: hover between rows and click the plus button that appears. * **Move a widget**: drag it to another cell. Dropping it on an occupied cell swaps the two widgets. * **Resize a widget**: drag its edge handle to make it span more or fewer columns. * **Delete a row**: use the bin icon on the row. If the row contains widgets, you'll be asked to confirm. * **Start over**: use the Reset view option in edit mode to return to the default layout. ### How to Add a Widget 1. **Start**: in edit mode, click an empty cell marked "Add". 2. **Choose a widget**: pick a chart or stat type, or one of the standard components. A search box helps you find things quickly. 3. **Connect to data**: for charts and stats, choose the source the data comes from: Sessions, Requests, Data Tables, Tracked Metrics, or Activity. 4. **Shape the result**: set what to count or measure, what to split it by, and how it should look. 5. **Finish**: click "Add Widget". You can reopen any widget later to edit or delete it. While connecting a widget to data you can also set: * **Widget filters**: only rows matching your filters are counted. Options include time range, environment, status, trigger type, workflow, and users. * **Data scope**: use all data or limit the widget to specific workflows, with an option to compare workflows against each other. * **Date range**: from Today through Last 7 days and This month up to All time. * **Target**: give a metric a goal, and the widget shows progress towards it. * **Custom title**: name the widget yourself instead of using the generated one. ### Visualisation Types Widgets come in several visual forms: * **Stats**: Big Number and Progress bar, for single headline figures. * **Charts**: Bar chart, Line chart, Area chart, Horizontal bar, and Scatter, for comparisons and trends. * **Proportions**: Pie chart, Donut chart, and Funnel, for how a whole breaks down. * **Browse**: Table, for scanning individual rows of data. ### Generating Widgets with AI Instead of configuring a widget by hand, choose **Generate with Lleverage** in the widget picker and describe the insight you want in plain language, for example "Show me the time saved this month with a trend compared to last month". Press Generate and the widget is built for you, ready to tweak like any other. You can also switch on **AI insight** when setting up a widget. This adds a short AI-generated comment to the widget that explains what the data shows. > πŸ’‘ If a search in the widget picker comes up empty, generating is a quick way to build exactly what you had in mind. ### Standard Components Alongside data widgets, the picker offers ready-made components you can drop straight onto the dashboard: * **Agent Chat**: start a message to the project's agent. * **Recently Opened**: jump back to things you were working on. * **Workflows**, **Apps**, **Sessions**, **Requests**, **Notifications**, **Knowledge Bases**, **Data Tables**, **Project Members**: browsable lists of those areas of the project. * **Failed Runs** and **Successful Runs**: recent run outcomes at a glance. * **Quick Links**: a set of shortcuts you define. * **Text Block**: your own text, for guidance or announcements. * **Navigation Button**: a prominent button that takes people to a page you choose. > πŸ’‘ Some components are only available in Builder View or when the related feature is enabled in your project. ### Dashboards on the Monitor Tab The project dashboard is the project's home surface. The Monitor tab has its own dashboard, built with the same widget system but focused on run analytics: each saved view there carries its own layout of stat cards, charts, and the activity table, edited with the pencil button and saved with "Update view". Charts built on the Monitor tab can be pinned to the project dashboard with the pin button (Pin to dashboard). A chart pinned from a saved view stays in step with that view's filters; otherwise it keeps the filters that were applied when you pinned it. > πŸ’‘ Build run analytics on the Monitor tab, then pin the charts worth seeing every day to the project dashboard. See [Activity Monitoring](/platform/activity-monitoring) for the Monitor tab itself. # Navigation Each project's sidebar can be tailored to how that project is used. You can choose between two layouts, decide where people land when they open the project, pin any page to the sidebar, and control which help options appear. Most of this is managed in the project's settings; pinning happens straight from page headers. ### Key Features * Two sidebar layouts: Agent and Workflows * A default page setting that decides where people land * Pinned pages with custom labels, icons, and collapsible groups * Quick access to saved views from the sidebar * Configurable help options at the bottom of the sidebar ### Layouts Open the project's settings and go to the **Navigation** tab. Under Customise Sidebar, the **Layout** setting offers two presets: * **Agent**: an agent-first sidebar, and the default for new projects. It removes Dashboard, Apps, Sessions, and Requests from the sidebar so the agent takes centre stage. * **Workflows**: the classic workflow-building sidebar. It removes the Agent items and keeps the familiar building and monitoring pages. > πŸ’‘ The layout applies to everyone in the project, so pick the one that matches how the project is mostly used. ### Default Page The **Default page** setting, on the General tab of the project's settings, decides where people land when they open the project. Depending on the layout, you can choose Dashboard, Agent, Requests, or any pinned page. > πŸ’‘ You can also make a pinned page the landing page directly from its pin dialog, using the "Default page" toggle. ### How to Pin a Page Almost any page in a project can be pinned to the sidebar, so the pages a team uses most are always one click away. 1. **Open the page** you want to pin and click the pin button in its header. 2. **Name it**: give the pin a label (up to 40 characters). 3. **Pick an icon** so it's easy to spot in the sidebar. 4. **Click Pin**: the page appears in the sidebar for everyone in the project. To change or remove a pin, click the pin button again on that page and edit the details or choose Unpin. Some lists, such as workflows and data tables, also offer "Pin to sidebar" in their menus. > ⚠️ A project can have up to 30 pins. Pinning is available to builders and up. ### Grouping Pins Pins can be organised in the **Pins** tab of the project's settings, where you can rearrange, rename, group, or remove them. 1. **Create a group**: click "New group" and give it a name. 2. **Fill it**: drag pins below the group row to move them into it. 3. **See it in the sidebar**: the group becomes a collapsible heading that people can expand and collapse. > πŸ’‘ Removing a group doesn't remove its pins; they just become ungrouped again. ### Saved Views in the Sidebar In the Agent layout, hover over Monitoring in the sidebar to see your saved activity views and jump straight to a filtered view of your runs. ### Help Options The Navigation tab also controls which help options show in the sidebar: * **Chat Support**: let people reach chat support from the sidebar. * **Report Bug**: let people report a bug from the sidebar. * **External Support Link**: add your own link, such as an internal help desk, with a custom label (up to 20 characters). It opens in a new tab. The same tab includes display options for the sidebar's sessions list, such as whether people can filter it and how it's grouped and sorted by default. > πŸ’‘ Project owners manage these settings, so a project shared with a wider team can present exactly the support routes that team should use. # Activity Monitoring The Activity tab provides comprehensive analytics and monitoring for all your workflow executions. Track performance, identify issues, and analyse usage patterns across your organisation with detailed run history, powerful filtering, and customisable saved views. > πŸ’‘ In projects using the agent-first navigation, this tab is called **Monitor**. The functionality is the same. ### Key Features * Real-time workflow execution tracking * Detailed run history with status monitoring * Advanced filtering, including metrics and session lookups * Saved views with pinning and locked filters * Customisable dashboard with stat cards and charts * User feedback collection and analysis * Run trace analysis for debugging * Export and sharing capabilities ### How to Access Activity Monitoring 1. Navigate to the main Lleverage interface 2. Click on the "Activity" tab in the navigation menu 3. The default "All Activity" view loads, showing the last 30 days of Live (production) runs 4. View your workflow runs in the activity table > πŸ’‘ The Activity tab updates in real-time as workflows execute, giving you live insights into your automation performance. ### Understanding the Activity Table #### Table Columns * **Timestamp**: When the workflow run started * **Workflow**: Name of the workflow that was executed * **User**: Who triggered or actioned the workflow * **Status**: Current state of the run * Success - Completed successfully * Failed - Encountered an error * Paused - Waiting, for example on human input * Aborted - Manually stopped * Timeout - Ran out of time * Running - Currently executing * **Type**: How the workflow was triggered * App (Form or Chat interface) * API * Schedule * Integration * Data Table * **Environment**: Live (production) or Builder (test runs from the workflow builder) * **Feedback**: User ratings and comments on the workflow execution * **Run Time**: Duration of the execution > πŸ’‘ You can filter directly from the table: column headers for status, type, environment, user, feedback, and action type include a "Filter by" option. #### Choosing What Each Row Represents Use the **Breakdown by** control in the toolbar to switch what the table shows: * **Session**: One row per session (default) * **Execution**: One row per workflow execution * **Action**: One row per individual action The **Group by** control changes the time bucketing of the charts between Day, Week, and Month. ### How to Filter Activity Data Click the **Filter** button to open the filter menu, then pick a category. Active filters appear as chips next to the button. #### Available Filters * **Date**: Last 24 hours, Last 7 days, Last 30 days (default), Since, or a custom range * **Workflow**: Select specific workflows to monitor * **Status**: Success, Failed, Paused, Aborted, Timeout, or Running * **Type**: Filter by trigger type (App, API, Schedule, Integration, Data Table) * **Users**: View runs by specific users or API keys * **Feedback**: Positive, Negative, or Any Feedback * **Action Type**: Filter by the types of actions used in the run * **Environment**: Live or Builder * **Session ID**: Paste a session ID to jump straight to a specific session * **Metrics**: Each metric configured in your project gets its own filter, with operators such as Equals, Contains, and Greater than * **Advanced**: Field-based criteria, such as Duration (ms) #### How to Apply Filters 1. Click the "Filter" button in the filter bar 2. Select a category and choose your options 3. Multiple filters can be combined for precise results 4. The table and charts update automatically as filters are applied 5. Remove a chip to clear that filter > πŸ’‘ Combine multiple filters to investigate specific issues, such as all failed API calls in the last 24 hours. Your current filters are reflected in the page URL, so you can share the link with a team member and they'll see the same view. ### How to Use Workflow Feedback #### Understanding Feedback Users can provide feedback on workflow runs to help improve automation quality: * **πŸ‘ Thumbs up**: Indicates a positive experience * **πŸ‘Ž Thumbs down**: Indicates issues or dissatisfaction * **πŸ’¬ Comments**: Additional context about the experience #### How to Filter by Feedback 1. Click on the Feedback filter 2. Select from the available options: * **Positive**: Shows only runs with thumbs up * **Negative**: Shows only runs with thumbs down * **Any Feedback**: Shows all runs with any type of feedback 3. Combine with other filters to analyse specific feedback patterns > πŸ’‘ Use feedback filters to identify workflows that may need improvement or to highlight successful automations for replication. ### How to Use Saved Views Saved views appear as tabs at the top of the Activity page. Every project starts with a default **All Activity** view, and you can create as many additional views as you need. #### Creating a Saved View 1. Click the "+" button next to the view tabs 2. Give your view a name and an optional description 3. Choose the filters the view should apply 4. Click "Create" β€” the view appears as a new tab #### Understanding Locked Filters When a saved view is active, the filters that are part of the view appear as locked chips with a dashed border. They can't be removed or edited directly β€” hovering shows "This filter is part of the saved view". * You can still **add** filters on top of a locked filter; your additions appear as a separate, editable chip * To change the view's own filters, right-click the view tab and choose **Edit**, or make your changes and click **Update view** in the toolbar to save them into the view > ⚠️ This applies to the default "All Activity" view too: its Date and Environment filters are locked. Add your own filters on top, or create a new view for a different baseline. #### Managing Views Right-click a view tab to: * **Pin to sidebar**: Quick access from the navigation * **Edit**: Change the view's name, description, and filters * **Delete**: Remove the view (the default view can't be deleted) A view remembers more than filters: column layout, grouping, row size, charts, and dashboard layout are all saved with it. When you've changed any of these, click **Update view** to persist your changes. #### Benefits of Saved Views * Quick access to frequently used filter combinations * Consistent monitoring across team members * Foundation for setting up alerts * Time-saving for regular reporting > πŸ’‘ Create saved views for common monitoring scenarios like "Daily Failed Workflows" or "High-Volume API Calls". ### Understanding the Monitoring Dashboard The area above the table is a customisable dashboard. By default it shows four stat cards based on your current filters: * **Total Sessions**: Overall workflow sessions * **Successful**: Runs that completed successfully * **Failed**: Runs that encountered an error * **Avg Duration**: Mean execution time #### Charts The **Runs vs Errors** chart is shown by default. Use the edit (pencil) button to add more: * **Timeline**: Visualise run patterns over time * **Successful Runs** and **Failed Runs**: Track outcomes separately * **Avg Duration**: Spot performance trends * **Feedback**: Track ratings over time * **Metric charts**: One available per metric configured in your project Click a bar in any chart to focus the whole page on that time bucket β€” a "Focus" chip appears in the filter bar, and you can remove it to zoom back out. > πŸ’‘ Charts can also be pinned to your project dashboard, so key trends are visible as soon as you open the project. #### Customising the Layout 1. Click the edit (pencil) button in the toolbar 2. Add, move, or resize cards, charts, and the activity table 3. Click "Done editing" to finish, then "Update view" to save the layout into the current view ### How to Analyse Individual Runs #### Viewing Run Details 1. Click on any row in the activity table 2. A detailed view opens showing: * Complete input data provided by the user * Full output returned by the workflow * Execution traces for each step * Error messages if applicable * User feedback if provided #### Using Trace Analysis 1. In the run details, click on "Traces" 2. View the step-by-step execution path 3. See inputs and outputs for each action 4. Identify where failures occurred 5. Understand processing time for each step > ⚠️ Trace analysis is invaluable for debugging complex workflows and optimising performance. ### How to Export Activity Data 1. Apply your desired filters 2. Click the "Export" button in the toolbar 3. Choose "Export CSV" or "Export Excel" > πŸ’‘ Exports respect your current filters, making them perfect for reporting on exactly the runs you're looking at. ### Best Practices #### For Performance Monitoring * Regularly review average duration metrics * Investigate workflows with increasing run times * Set up saved views for performance tracking * Monitor failed run patterns for systemic issues #### For Debugging * Use trace analysis for failed runs * Use the Session ID filter to jump straight to a reported session * Compare successful vs failed runs * Look for patterns in failure times or users * Review user feedback for additional context #### For Reporting * Create saved views for standard reports * Export data as CSV or Excel for external analysis * Use charts for stakeholder updates * Track trends over custom date ranges * Include feedback analysis in quality reports #### For Continuous Improvement * Regularly analyse negative feedback * Identify workflows with low satisfaction rates * Use positive feedback to understand best practices * Act on user comments and suggestions > πŸ’‘ The Activity tab is your command centre for workflow operations. Regular monitoring helps maintain reliable automation performance and user satisfaction. # Request Inbox The Request Inbox is your centralised hub for managing all human-in-the-loop tasks created by your workflows. It provides a unified interface to view, action, reassign, and track the history of all approval requests and input forms assigned to you or your team. ### Overview When workflows reach human-in-the-loop actions like Request Approval or Request Input, they create requests that appear in the Request Inbox. This ensures that critical human decisions and data collection don't get lost while maintaining workflow efficiency. ### Key Features * **Centralised Task Management**: All human-in-the-loop requests in one location * **Reassignment**: Hand a request to a different person or role * **Notes and Mentions**: Discuss a request's linked record with your team * **Inline Feedback**: Rate AI-generated content directly inside a request * **Notifications**: In-app and email alerts for new and reassigned requests * **Complete Audit Trail**: Track all decisions, submissions, and reassignments * **Powerful Filtering and Saved Views**: Organise requests your way * **Real-time Updates**: Workflow continuation upon request completion ### How to Access the Request Inbox **How to open your Request Inbox** 1. Navigate to the main Lleverage interface 2. Look for the "Requests" tab in your navigation menu 3. Click on the "Requests" tab to open your inbox 4. The inbox displays all requests assigned to you > πŸ’‘ **Tip**: You can also access the Request Inbox directly from email notification links for faster task completion. ### Understanding the Request Inbox Interface #### Inbox Tabs The tabs at the top of the inbox split your requests by type: * **All**: Every request visible to you * **Approvals**: Decision requests only * **Inputs**: Input form requests only * **Mentions**: Requests where someone has mentioned you in a note Any saved views you create appear as extra tabs after these. #### Request Statuses * **Open**: Waiting for someone to action it * **Completed**: Actioned β€” for approvals, the status shows the decision that was made (for example "Approved" or "Rejected"), along with any reason given * **Cancelled**: The request was cancelled * **Superseded**: A newer request for the same step replaced this one * **Failed**: The workflow behind the request hit an error (see Failed Requests below) ### How to Filter Requests Click the **Filter** button to open the filter menu. Active filters appear as chips. * **Assignee**: Filter by people or roles. By default you see requests for you and your role β€” clear this filter to see every request in the project (Builders and Owners only) * **Workflow**: Show requests from specific workflows * **Record**: Show requests linked to data table records β€” either a specific record, or any record matching a property value * **Status**: Attention Required, Completed, Cancelled, Superseded, or Failed * **Date Range**: Last 24 hours, Last 7 days, Last 30 days, or a custom range * **Created By**: Who triggered the request * **Type**: Decision or Input * **My Status**: Requests where you were Mentioned, or have Replied * **Hide Completed / Hide Responded**: On by default, to keep your inbox focused * **Show Archived**: Include archived requests > πŸ’‘ **Best Practice**: Use the Record filter to see every request that touches a particular record β€” for example, all requests for one supplier or one invoice. #### Saved Views 1. Apply your desired combination of filters 2. Click the "Save filter" button in the filter bar 3. Your saved view appears as a new tab 4. Right-click a saved view tab and choose "Set as default landing view" to make it the tab that opens first β€” it's marked with a small house icon ### How to Action Requests #### For Approval Requests **How to complete approval requests** 1. Click on an open approval request to open it 2. Review the provided information: * Title and description from the workflow * Any context or data from previous workflow steps * Available action buttons with different styling 3. Click the appropriate button to make your decision 4. The request status updates immediately 5. The workflow continues based on your selection > ⚠️ **Important**: Once you click an approval button, the action cannot be undone. Review all information carefully before making your decision. #### For Input Requests **How to complete input requests** 1. Click on an open input request to open it 2. Review the request description and context 3. Fill out all required form fields (marked as mandatory) 4. Complete optional fields if applicable 5. Click "Submit" to complete the request 6. The workflow continues with your provided data > πŸ’‘ **Form Completion Tip**: Required fields are clearly marked and must be completed before submission. Save time by gathering all necessary information before starting the form. > ⚠️ **Read-only requests**: Builders and Owners can view every request in the project, but a request can only be submitted by someone assigned to it. Requests you aren't assigned to open in read-only mode. ### How to Reassign a Request Requests can be handed to a different person or role β€” useful for holiday cover, workload balancing, or escalation. **How to reassign a request** 1. Open the request 2. Click the assignee avatars at the top of the request, then choose "Edit Assignee" 3. Tick the people who should be assigned (at least one is required) 4. Click "Save" You can also click the pencil icon on the "Requested input from…" bar inside the request, which additionally lets you assign to a whole role (Owner, Builder, Operator, or Member) instead of specific people. After reassigning: * Newly assigned people receive an in-app notification and an email * The reassignment is recorded in the request's history, showing who reassigned it and to whom > πŸ’‘ **Who can reassign**: Reassignment is available to Builders and Owners, and only on open or failed requests. ### How to Add Notes When a request is linked to a data table record, you can discuss it with your team using notes on that record. **How to add a note** 1. Open the request 2. Open the linked record β€” click the record chip above the request, or find it under "Records" in the request sidebar 3. Go to the "Comments" tab 4. Click "Add note", write your note, and submit Notes support **@ mentions** β€” type @ to mention a teammate: * Mentioned teammates get a notification, and the request appears in their **Mentions** tab * Other assignees are notified of new notes too * Notes on a record are visible to everyone in the project, across every request that touches that record * You can edit or delete your own notes > πŸ’‘ **Tip**: Use the "My Status" filter to find requests where you've been mentioned or have replied. ### How to Give Feedback You can rate AI-generated content directly inside a request, helping builders improve the workflow. **How to give feedback** 1. Hover over an AI-generated element inside the request 2. Click thumbs up ("Good response"), thumbs down ("Bad response"), or the comment icon for general feedback 3. Add an explanation in the text box 4. Click "Submit" You can also select a specific piece of text inside the element first β€” the feedback popover lets you attach your comment to exactly that part of the response. Feedback lands in the workflow's Feedback panel in the builder, where builders can review it, mark it resolved, and use it to improve the workflow. > πŸ’‘ **Why it matters**: Concrete feedback on real requests is the fastest way to make the automation better for everyone. ### Failed Requests If the workflow behind a request hits an error, the request is marked **Failed** and shows a banner explaining what went wrong. * Failed requests stay actionable: submit it again to retry the workflow from that step * Or archive the request to clear it from the queue * Failed requests can still be reassigned ### How to Re-open a Completed Request If a flow needs to be rewound β€” for example, a decision was made with the wrong information β€” a completed request can be re-opened. 1. Open the completed request 2. Open the request's menu and choose "Re-open Request" 3. A fresh open request is created for the same step, keeping the original assignees and details 4. Answering it again resumes the flow from this step > ⚠️ **Important**: Re-opening supersedes any other requests that were still open later in the same session β€” they'll show as "Superseded". ### Archiving Requests Use **Archive Request** in the request's menu to clear a request from the queue without actioning it. Archived requests show who archived them and when, can be brought back with "Unarchive", and can be found again using the "Show Archived" filter. ### The Request Sidebar Open the sidebar from the "Request" button on an open request to see: * **Records**: Data table records linked to this request * **Attachments**: Files attached to the request * **History**: The full timeline β€” creation, steps that ran, reassignments, submission, and archiving, each with who did it and when > πŸ’‘ **Compliance Benefit**: The history gives you a complete audit trail for every request, which helps with compliance requirements and troubleshooting. ### Notifications and Alerts #### Email Notifications You receive an email when: * A new request is assigned to you * A request is reassigned to or away from you Each email includes the request details and a "View Request" button that takes you straight to it. Depending on your notification preferences, emails arrive immediately or as a digest. #### In-Platform Notifications * **Badge Indicators**: The Requests tab shows your pending request count * **Assignment Alerts**: "New request assigned to you" notifications with a direct link * **Mention Alerts**: Notifications when someone mentions you in a note * **Real-time Updates**: New requests appear immediately, and completed ones update instantly > πŸ’‘ **Stay Connected**: Check your notification settings to ensure you don't miss critical approval requests or time-sensitive input needs. ### Getting Help Need help while working through requests? Click the **"Chat with us"** bubble in the sidebar to open the support chat: * Ask anything about Lleverage β€” the assistant answers instantly, and knows which page you're on * Click **"Talk to a Human"** at any point to bring the Lleverage team into the conversation * Use **"Report an issue"** next to the chat bubble to file a bug * If a request shows an error, use the "Report a bug" button on the error itself β€” it sends the technical details along automatically ### Best Practices #### For Efficient Task Completion * **Review Thoroughly**: Read all provided information before taking action * **Act Promptly**: Complete requests quickly to avoid workflow delays * **Provide Quality Input**: Ensure accuracy and completeness for input requests * **Verify Decisions**: Double-check approval choices before confirming #### For Effective Inbox Management * **Regular Monitoring**: Check your Request Inbox at consistent intervals * **Use Saved Views**: Save your common filter combinations and set your default landing view * **Keep It Tidy**: Archive requests that no longer need action * **Review Patterns**: Monitor completed requests to identify process improvements #### For Team Collaboration * **Reassign Rather Than Wait**: Hand requests over for holiday cover or workload balancing * **Use Notes and Mentions**: Keep the discussion on the record where everyone can see it * **Assign to Roles**: Role-based assignment spreads work across the team automatically * **Give Feedback**: Rate AI-generated content so builders can keep improving the workflow > πŸ’‘ **Workflow Success**: The Request Inbox is essential for maintaining smooth human-in-the-loop workflows. Regular monitoring and prompt action ensure your automated processes run efficiently while preserving necessary human oversight. ### Troubleshooting **Common Issues and Solutions** **Not receiving request notifications** * Check your notification settings in your user profile * Verify you're assigned to the correct role or user group * Confirm your organisation permissions **Requests not appearing in inbox** * Check the "Hide Completed" and "Hide Responded" filters β€” they're on by default * Check if you're viewing the correct organisation/project * Remember that non-Builders only see requests assigned to them **Cannot complete a request** * You can only submit requests you're assigned to β€” others open read-only * Check if the request has already been completed or superseded by someone else * Verify all required fields are filled correctly # Alerts System The Alerts system enables proactive monitoring of your workflows by notifying you when specific conditions occur. Built on top of saved views, alerts help you stay informed about critical events, performance issues, or unusual activity patterns without constant manual monitoring. ### Key Features * Automated notifications based on saved view criteria * Email alerts for workflow events * Customisable alert conditions * Integration with Activity saved views * Team-wide alert management * Real-time monitoring capabilities ### Understanding Alert Prerequisites #### Saved Views Requirement Alerts are created from saved views in the Activity tab: 1. You must first create a saved view with specific filters 2. The saved view defines what conditions trigger the alert 3. Alerts monitor for any activity matching the saved view criteria > ⚠️ You cannot create alerts without first setting up a saved view in the Activity tab. ### How to Create Alerts #### Step 1: Prepare Your Saved View 1. Go to the Activity tab 2. Apply filters for the conditions you want to monitor 3. Save the view with a descriptive name 4. Ensure the view captures the exact criteria for your alert #### Step 2: Navigate to Saved Views 1. Click on the "Saved Views" tab in the navigation 2. You'll see a list of all your saved views 3. Each saved view displays its filters and creation details #### Step 3: Create an Alert 1. Find the saved view you want to create an alert for 2. Look for the bell icon next to the saved view 3. Click the bell icon to open alert configuration 4. Configure your alert settings: * Alert name * Notification recipients * Frequency settings 5. Save the alert configuration > πŸ’‘ Name your alerts clearly to indicate what they monitor, such as "Failed Production Workflows" or "Long-Running API Calls". ### How to Manage Existing Alerts #### Viewing Active Alerts 1. In the Saved Views tab, alerts are indicated by active bell icons 2. Click on an alert to view its configuration 3. See when the alert was last triggered 4. Review the underlying saved view criteria #### Modifying Alerts 1. Click on the bell icon of an existing alert 2. Update the alert configuration: * Change recipients * Modify notification settings * Update the alert name 3. Save changes to update the alert #### Disabling or Deleting Alerts 1. Click on the active bell icon 2. Choose to either: * Disable temporarily (alert can be re-enabled) * Delete permanently 3. Confirm your action > ⚠️ Deleting an alert is permanent, but the underlying saved view remains intact. ### Understanding Alert Notifications #### What Triggers Notifications Alerts send notifications when: * New activity matches your saved view criteria * The specified conditions are met * Based on your configured frequency settings #### Notification Contents Alert emails include: * Alert name and description * Number of matching activities * Direct link to view the activities * Summary of the filter criteria * Timestamp of the alert > πŸ’‘ Click the link in alert emails to go directly to the filtered activity view. ### Common Alert Scenarios #### Performance Monitoring **Saved View**: Workflows with run time > 5 minutes **Alert Purpose**: Identify performance degradation **Action**: Investigate and optimise slow workflows #### Error Tracking **Saved View**: Failed workflows in production **Alert Purpose**: Immediate notification of failures **Action**: Quick response to production issues #### Usage Monitoring **Saved View**: Specific workflow executions **Alert Purpose**: Track usage of critical processes **Action**: Ensure important workflows are being used #### Security Monitoring **Saved View**: Workflows run by external users **Alert Purpose**: Monitor external access **Action**: Verify authorised usage > πŸ’‘ Create multiple alerts for comprehensive monitoring coverage across different aspects of your operations. ### How to Use Saved Views Effectively #### Accessing Saved Views 1. Click on a saved view name to apply it instantly 2. The Activity tab opens with pre-selected filters 3. All relevant data is displayed immediately 4. Modify filters further if needed #### Managing Saved Views 1. Edit saved view names for clarity 2. Delete unused saved views to reduce clutter 3. Share saved views with team members 4. Create views specifically for alert purposes > ⚠️ Deleting a saved view will also delete any associated alerts. ### Best Practices #### For Alert Creation * Create specific, focused saved views for alerts * Test saved views thoroughly before creating alerts * Use descriptive names for both views and alerts * Document what each alert monitors and why #### For Alert Management * Review alerts regularly for relevance * Update recipient lists as team changes occur * Disable rather than delete alerts during testing * Consolidate similar alerts to reduce noise #### For Team Collaboration * Share alert configurations with team members * Document response procedures for each alert * Assign alert ownership for accountability * Regular review meetings for alert effectiveness #### For Optimal Monitoring * Balance coverage with alert fatigue * Start with critical alerts, expand gradually * Set appropriate frequency to avoid spam * Use different recipients for different severity levels > πŸ’‘ Well-configured alerts transform reactive troubleshooting into proactive system management, significantly improving workflow reliability. # Templates Templates provide pre-built workflow solutions that help you get started quickly with common automation scenarios. From simple tasks to complex integrations, templates eliminate the need to build workflows from scratch and demonstrate best practices for various use cases. ### Key Features * Pre-configured workflows for common business processes * Two types: Standard templates and AI-assisted templates * Searchable template library * Preview functionality before using * Customisable titles and configurations * Copilot integration for complex setups (temporarily unavailable while the Copilot is being improved) ### How to Access Templates 1. Click on the user menu at the bottom of the interface 2. Select "Templates" from the menu options 3. The template library opens, displaying all available templates 4. Browse or search to find the template you need > πŸ’‘ Templates are regularly updated with new options based on popular use cases and user requests. ### Understanding Template Types #### Standard Templates Pre-defined workflows that are ready to use immediately: * Complete workflow structure included * Basic configuration options * No additional setup required * Ideal for common, straightforward processes #### AI-Assisted Templates Templates that use Copilot for intelligent configuration: * Require interactive setup process * Copilot guides you through customisation * Often used for workflows needing authentication * More flexible and adaptable to specific needs > ⚠️ The Workflow Copilot is temporarily unavailable while it is being improved, so the Copilot-guided setup for AI-assisted templates is currently unavailable. Standard templates are unaffected and ready to use as normal. > ⚠️ AI-assisted templates may take longer to set up but provide more tailored solutions for complex requirements. ### How to Find the Right Template #### Browsing Templates 1. Scroll through the template library to see all options 2. Templates are organised by category and use case 3. Each template shows: * Template name * Brief description * Type indicator (Standard or AI-assisted) * Category tags #### Searching for Templates 1. Use the search bar at the top of the template library 2. Search by: * Template name * Use case keywords * Integration names * Business process terms 3. Results update as you type 4. Clear the search to return to the full library > πŸ’‘ Try different search terms if you don't find what you need immediately - templates may be tagged with multiple relevant keywords. ### How to Use a Template #### Step 1: Select a Template 1. Click on the template card you want to use 2. A preview window opens showing: * Full template description * Workflow structure overview * Required integrations or configurations * Expected inputs and outputs #### Step 2: Preview the Template 1. Review the workflow structure in the preview 2. Check if it matches your requirements 3. Note any integrations or authentications needed 4. Decide if this template suits your needs #### Step 3: Configure the Template For Standard Templates: 1. Enter a custom title for your workflow 2. Click "Use Template" to create your workflow 3. The workflow opens in the canvas with the template structure 4. Make any necessary adjustments to fit your specific needs For AI-Assisted Templates: 1. Enter a custom title for your workflow 2. Click "Use Template" to start the setup 3. Copilot activates in the canvas 4. Follow Copilot's prompts to: * Configure authentication settings * Customise workflow parameters * Set up integrations * Define specific business logic 5. Copilot builds the workflow based on your inputs > ⚠️ The Copilot-guided setup is temporarily unavailable while the Workflow Copilot is being improved, so these steps do not currently apply. Standard templates work as normal. > πŸ’‘ AI-assisted templates are particularly useful when you need to connect to external services that require authentication. ### Working with Template-Based Workflows #### Customising After Creation Once a template creates your workflow: 1. All standard editing features are available 2. Add, remove, or modify actions as needed 3. Change connections between nodes 4. Update configurations to match your requirements 5. The workflow is completely yours to modify #### Maintaining Template Structure Consider keeping the core template structure when: * The template represents best practices * You want to maintain consistency across similar workflows * Future updates might benefit from the standard structure > ⚠️ Heavily modified templates may not benefit from future template improvements or updates. ### Common Template Categories #### Business Process Automation * Approval workflows * Document processing * Email automation * Report generation #### Integration Templates * CRM synchronisation * Data migration between systems * API connections * Database operations #### AI-Powered Templates * Content generation * Data analysis * Classification tasks * Intelligent routing #### Communication Templates * Notification systems * Chat integrations * Alert mechanisms * Feedback collection > πŸ’‘ Each category contains multiple specific templates addressing various business needs. ### Best Practices #### For Template Selection * Read descriptions carefully before selecting * Check integration requirements upfront * Consider if a template needs heavy modification * Look for templates matching your industry or use case #### For Template Usage * Always customise the title meaningfully * Test the template with sample data first * Document any significant modifications * Save your customised version for team reuse #### For AI-Assisted Setup These apply when the Workflow Copilot returns; the Copilot-guided setup is temporarily unavailable while it is being improved. * Have authentication credentials ready * Provide clear, specific information to Copilot * Review Copilot's configurations before accepting * Test authentication connections immediately #### For Team Collaboration * Share successful template implementations * Document which templates work well for your processes * Request new templates for common team needs * Create internal documentation for customised templates > πŸ’‘ Templates are starting points, not rigid solutions. Feel free to adapt them to perfectly match your workflow requirements. # Data Tables Data Tables in Lleverage allow you to store, manage, and work with structured data directly within your projects. You can bring data in from files or workflows, organise it with customisable columns, link records across tables, collaborate through comments and requests, and connect everything to your workflows. ### Key Features * Flexible data storage with a wide range of column types, including files, users, and links between tables * Multiple import options (CSV, XLSX, XLS, JSON) with column mapping and per-row error reporting * Export to CSV, XLSX, or JSON * Saved views with filters, sorting, and column visibility * A board view for working with records as cards grouped by status * Comments, linked requests, and a change timeline on every record * Row locking, pinning, and de-duplication controls * Ready-made table templates and one-click table duplication * Full workflow integration with triggers and actions ### How to Create a Table 1. **Open Data Tables** in your project. 2. **Choose how to start:** * **Import Data** – upload a file and create a table from its contents * **Use a Template** – start from a ready-made table template for common use cases * **Start from Scratch** – create a blank table and define your own columns 3. **Add columns and records** to shape your table. > πŸ’‘ When you create a blank table, Lleverage automatically suggests a title and description for it once you've added columns, so you don't have to start with naming. You can also **duplicate an existing table** from the table list. Duplication runs in the background and you'll be notified when the copy is ready. ### Interface Overview When you open a Data Table, the interface is organised as follows: * **Header:** The table name (click it to open table settings), your view tabs, and a button to add a new record. If you've told Lleverage what your records are called, the button uses that name, for example "New Invoice" instead of "New Record". * **Toolbar:** Filter, search, row density (Compact, Standard, or Spacious), column visibility, create view, export, and a Columns button for managing columns and switching between the list and board layouts. * **Filter chips:** When filters are active, they appear as chips below the toolbar with a Reset option. * **Bottom bar:** The record count, a completion indicator showing what percentage of the table is filled in, a shortcut for setting up automations on this table, and pagination controls. ### How to Access Table Settings 1. **Open your Data Table.** 2. **Click the table name** in the top left corner. 3. **Adjust the settings** in the popover: * **Pin to sidebar** – pin this table for quick access * **Description** – describe what the table is for * **Records are called** – a single word for what each row is (for example "invoice"), used for buttons like "New Invoice" * **Add rows manually** – allow users to add new rows to the table * **Read-only mode** – lock the table from editing * **Remove duplicate rows** – automatically remove duplicate rows based on a selected column * **Linked Workflow** – see and open any workflows triggered by this table > πŸ’‘ To rename your table, click directly on the table name at the top of the screen and type the new name. > ⚠️ The duplicate-removal setting cannot be changed once the table is running. ### How to Create and Manage Views Views let you save different perspectives of your data without modifying the underlying table. A view remembers its filters, sorting, and which columns are visible. The "All" view is always available and shows every record. 1. **Set up the table how you want it** – apply filters, sorting, and column visibility. 2. **Click the Create view button** in the toolbar. 3. **Name your view** and fine-tune its filters if needed. 4. **Choose the sharing options:** * **Visible for everyone** – share the view with the rest of your team * **Set as default view** – make this the view people land on 5. **Save.** The view appears as a tab next to "All". Each view has a menu where you can **Edit**, **Duplicate**, or **Delete** it. > πŸ’‘ When a view has its own filters, they appear as locked chips in the filter row. You can layer extra filters on top, and Reset takes you back to just the view's filters. ### Grid and Board Layouts Tables can be displayed as a standard grid or as a board of cards, similar to a kanban board. 1. **Click the Columns button** in the toolbar. 2. **Under "View", choose List or Kanban.** On the board: * Records are grouped into columns by a **Single Select** column. Use the "Group by" selector in the toolbar to choose which one. * **Drag a card** to another column to update that record's value. * **Click a card** to open the record's details. > ⚠️ The board needs at least one Single Select column in your table. If there isn't one, add it first. ### How to Add a New Record 1. **Click the new record button** in the top right corner (for example "New Record" or "New Invoice"). 2. **Fill in the fields** in the form and save. > πŸ’‘ The form also has an "Import from file" option if you'd rather bring in many records at once. ### How to Add Columns 1. **Click the Add Column button** at the right-hand end of the table (or use "Insert 1 column left" / "Insert 1 column right" from an existing column's menu). 2. **Name the column** and optionally add a description. 3. **Select the column type:** * **Text** – free text * **Number** – numeric values, with formatting options such as currency or percentage * **Toggle** – on/off values * **Date** – dates * **Single Select** – one choice from a set of options, each with its own colour * **Multi Select** – multiple choices from a set of options * **List** – a list of values * **Array** – a collection of structured values * **Object** – structured data * **File** – file attachments uploaded to the record * **User** – a person from your organisation * **Relationship** – a link to records in another table 4. **Optionally add example values** to guide AI extraction into this column. 5. **Save the column.** ### How to Edit Columns Open a column's menu from its header to: * **Edit column** – change the display name, description, and examples * **Insert 1 column left / right** * **Change colour** – highlight the column with a colour * **Format** – for Number columns, choose how values display (currency, percentage, and so on) * **Change type** – convert the column to a different type * **Duplicate** the column * **Sort** ascending or descending * **Filter on this column** * **Lock Column / Unlock Column** – prevent the column from being edited * **Hide** the column * **Delete** the column You can also drag column headers to reorder them, or open the **Columns** dialog from the toolbar to rearrange, edit, and delete columns in one place. The **column visibility** button in the toolbar controls which columns are shown. ### Changing a Column's Type When you change a column's type, Lleverage analyses your existing data before anything is converted: 1. **Choose "Change type"** from the column menu and pick the new type. Options that could lose data are marked. 2. **Review the analysis** – you'll see any warnings plus sample conversions showing original and converted values side by side. 3. **Confirm to run the conversion.** It runs in the background, and you'll see how many values were converted, skipped, or failed. ### Relationships Between Tables Relationship columns link records in one table to records in another, for example linking invoices to suppliers. 1. **Add a column** and choose the **Relationship** type. 2. **Configure the relationship:** pick the table to link to, the kind of relationship (One to One, One to Many, Many to One, or Many to Many), and which field from the linked table to show. 3. **Link records** by clicking the cell and searching for the record you want in the record picker. Linked records appear as badges in the cell, and you can hover or click them to preview the linked record. You can also filter on relationships using "Is linked to" and "Is not linked to" conditions. ### File Columns File columns let you attach files directly to records. Click the cell (or the field in the record form) and upload a file; it's stored with the record and can be previewed and downloaded later. ### How to Work with Rows **Right-click any row** for quick actions: * **View Details** – open the record's side panel * **Filter on this Row** – filter the table to matching records * **Duplicate** the record * **Lock Row / Unlock Row** – locked rows can't be edited until unlocked * **Pin** the row to keep it at the top * **Hide** the row * **Delete** the record #### Bulk actions Select multiple rows to act on them together: * **Delete** – remove all selected records * **Update field** – set one field to the same value across the selection * **Duplicate** – copy the selected records * **Lock / Unlock** – lock or unlock the selection in one go * **Copy ID** – copy the selected record IDs * **Run** – run row-level automation (requires a workflow trigger set up for this table) > ⚠️ Locked rows are skipped by bulk field updates, and deleting records cannot be undone. #### Pagination The bottom of the table shows pagination controls where you can navigate between pages and set the number of records displayed per page. ### Record Details, Comments, and Requests Open a record (via View Details or by clicking a board card) to see its side panel with four tabs: * **Details** – all the record's fields, editable in place * **Requests** – any workflow requests linked to this record, such as approvals waiting on it * **Timeline** – a history of the record: when it was created and updated, by whom, and any comments along the way * **Comments** – discuss the record with your team > πŸ’‘ The [Request Inbox](/platform/request-inbox) has a Record filter, so you can also work the other way round: see every request that touches a particular record from the inbox. ### Change History Lleverage keeps a history of changes to your data at the table, record, and field level, including what changed, who changed it, and when. The quickest way to review a record's history is the **Timeline** tab in its side panel. ### Removing Duplicate Rows To keep a table clean automatically, turn on **Remove duplicate rows** in the table settings. Duplicates are detected based on a selected column and removed automatically as data comes in. > ⚠️ This setting cannot be changed once the table is running, so decide on it early. ### How to Filter Records 1. **Click the Filter button** in the toolbar. 2. **Pick a column** and tick the values you want to see, or choose **Advanced** for more control. 3. **Active filters appear as chips** below the toolbar. Click a chip to adjust it, or click Reset to clear your filters. #### Advanced filters Advanced filters let you combine multiple conditions with "and"/"or" logic. The available conditions depend on the column type, for example: * **Text:** equals, contains, starts with, ends with, is empty, and more * **Number:** greater than, less than, and their variations * **Date:** on, before, after, on or before, on or after * **Toggle:** is true, is false * **Select and List columns:** includes, includes all, includes any * **Relationship:** is linked to, is not linked to ### How to Search Records Type in the **search box** in the toolbar and results filter in real time. ### How to Import Data 1. **Click the new record button**, then choose **Import from file**. 2. **Upload your file** – CSV, XLSX, XLS, or JSON. 3. **Pick a sheet** if your Excel file has more than one. 4. **Map your columns** – match the columns in your file to the fields in your table, or create new columns for anything unmatched. 5. **Start the import.** For large files you can choose **Import in Background** and keep working while it runs. 6. **Review the results** – when the import finishes, a summary shows how many records were imported and lists any rows that failed, with the reason for each. > πŸ’‘ The Import History for the table is shown inside the import dialog, so you can see previous imports and their outcomes in the same place. ### How to Export Data 1. **Click the Export button** in the toolbar. 2. **Choose a format:** CSV, XLSX, or JSON. 3. **Download your file.** The export covers all visible records, so filters are respected. ### Workflow Integration Data Tables integrate fully with Lleverage workflows, both as triggers and actions. > πŸ’‘ You can also set up an automation directly from the table itself, using the automation shortcut in the table's bottom bar: bring data in, send data out, or modify data whenever records change. #### How to Set Up a Data Table Trigger Use Data Table triggers to start a workflow when changes occur in your table. 1. **Add a new trigger** to your workflow and select the Data Tables trigger. 2. **Select the table** you want to monitor. 3. **Choose one or more events:** record created, record updated, or record deleted. 4. **Optionally add filter conditions** so the workflow only runs for records matching specific criteria. #### How to Create a Record Creates a new record in a specified table. 1. **Add the "Create Record" action** to your workflow. 2. **Select the target table.** 3. **Fill in the values** for each field, using variables to populate fields with dynamic data from your workflow. #### How to Find a Record Retrieves existing records from a table. 1. **Add the "Find Record" action** to your workflow. 2. **Select the table to search.** 3. **Choose your find method:** by record ID, or by filter conditions. 4. **Set the return mode:** first, last, all, or a specific position in the results. 5. **Configure the fail-on-empty behaviour** to decide what happens when nothing matches. #### How to Update a Record Modifies existing records in a table. 1. **Add the "Update Record" action** to your workflow. 2. **Select the target table.** 3. **Choose your update method:** by record ID, or by filter conditions. 4. **Enter the new values** for the fields you want to update. #### How to Delete a Record Removes records from a table. 1. **Add the "Delete Record" action** to your workflow. 2. **Select the target table.** 3. **Choose your deletion method:** by record ID, or by filter conditions. 4. **Configure the fail-on-empty behaviour.** > ⚠️ Deleted records cannot be recovered. Use filters carefully to avoid accidentally removing unintended data. ### Best Practices * Design your table structure thoughtfully before adding large amounts of data * Use descriptive column names and descriptions, and add example values to help AI fill columns accurately * Create views for different use cases rather than modifying the main table layout * Use Relationship columns instead of copying the same data into multiple tables * Lock rows or enable read-only mode to protect data that shouldn't change * Use filters in both views and workflow triggers to work with specific subsets of your data # Knowledge Bases Knowledge Base actions in Lleverage allow you to create, manage, and utilize collections of information that enhance your workflows with specialized content. These actions make it easy to store documents, add context, and reference specific information throughout your automations. ### Key Features * Document storage for various file types (PDFs, Word docs, CSV, JSON, XML, HTML) * Text content management for quick manual additions * Contextual knowledge that enhances AI capabilities * Searchable information accessible throughout workflows * Advanced configuration options to optimize information retrieval * Shared resources that can be used across multiple workflows *** ### How to Add Knowledge Base Actions 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one node to create a connection 2. Find Knowledge Base actions in: * The "All" tab * The "Tools" tab * The "Storing and Using Information" subcategory 3. Choose from the available Knowledge Base actions: * **Add Knowledge**: Store information in a Knowledge Base * **Search Knowledge Base**: Query and retrieve information 4. Click on your chosen action to add it to your canvas > πŸ’‘ **Tip**: These actions help you manage information within your workflows, making knowledge accessible when and where it's needed. *** ### How to Configure Add Knowledge Action **Setting Up the Basic Fields** 1. When you select the Add Knowledge action, you'll see three main fields: * **Content** (optional): The information you want to store * **Title** (optional): A descriptive name for the content * **Knowledge Base**: The destination folder (defaults to "knowledge base") **Selecting or Creating a Knowledge Base** 1. Click on the Knowledge Base dropdown 2. Select an existing Knowledge Base if available 3. Or click "Create Knowledge Base" to make a new one **If Creating a New Knowledge Base:** 1. A new Knowledge Base will be created (titled "Untitled" or named after your workflow) 2. Click the edit icon (cog) to customize your Knowledge Base 3. The Edit Knowledge Base modal will open with advanced options > πŸ’‘ **Tip**: Adding content to a Knowledge Base makes it available for your workflow to reference, similar to giving your workflow access to a specialized document library.

Add Knowledge Action

*** ### How to Configure Advanced Knowledge Base Settings **Primary Content Type Configuration** This setting determines how documents are processed and chunked for optimal retrieval: * **Auto**: Automatically detects the best content type and chunking strategy * **Structured Data**: For CSV, JSON, XML files with custom chunking to preserve data integrity * **Mixed/Web Content**: For webpages and HTML files with basic chunking (300 characters) * **Structured Documents**: For PDFs and Word docs, chunks by headings and sections (250 characters) * **Narrative Content**: For long-form text and articles with similarity-based chunking (350 characters) * **Transactional Documents**: For forms and receipts with no chunking (keeps documents intact) * **Conversational Content**: For chat logs and transcripts with similarity-based chunking (100 characters) * **Page-bound Content**: For presentations and page-based documents, chunks by page boundaries **Language Settings** 1. Default setting is "Multilingual" 2. This determines the embedding model used to vectorize your documents 3. Optimizes processing based on the language of your content **Adding Content to Your Knowledge Base** 1. **Upload Files**: Add documents directly from your computer 2. **Write Something**: Opens a text input to create content from scratch 3. After adding content, you can: * View uploaded files with checkmarks indicating successful upload * Delete items as needed * Rename your Knowledge Base > ⚠️ **Important**: Choose the appropriate Content Type based on the kind of information you're storing to optimize how the system processes and retrieves it. *** ### How to Configure Search Knowledge Base Action **Basic Setup** 1. Add the "Search Knowledge Base" action to your workflow 2. Configure the required **Query** field with your search terms 3. Select which **Knowledge Base** to search from the dropdown **Search Configuration Options** * **Match Search Results**: Set between 1-50 results (maximum 50, minimum 1) * **Search Fuzziness**: Scale from 0-100 * **0**: Keyword-based search (exact matches) * **100**: Semantic search (meaning-based matches) * **Mid-range**: Combination of both approaches **Using Search Results** 1. Connect the search results to other actions in your workflow 2. Typically used with AI actions that need contextual information 3. Results can be referenced using variables in subsequent workflow steps

Search Knowledge Action

*** ### How Knowledge Base Actions Work in Your Workflow **Use Case: Building a Knowledge Repository** 1. Add the "Add Knowledge" action to your workflow 2. Select or create a Knowledge Base 3. Configure content to be added (directly or via workflow variables) 4. When the workflow runs, information is automatically stored 5. Useful for: * Capturing important information during workflow execution * Building a Knowledge Base over time with new data * Creating a permanent record of workflow results **Use Case: Retrieving Contextual Information** 1. Add the "Search Knowledge Base" action to your workflow 2. Select which Knowledge Base to search 3. Configure the search query (can be dynamic based on workflow variables) 4. Connect search results to AI actions for enhanced responses 5. Useful for: * Providing context to AI prompts * Retrieving specialized information for decision-making * Creating responses based on your organization's knowledge > πŸ’‘ **Pro Tip**: Combining both actions allows you to build workflows that continuously learn and improve by adding new information and then accessing it when needed. *** ### Best Practices and Important Considerations **Knowledge Base Management** * Knowledge Bases are shared resources across multiple workflows * You can add multiple documents to a single Knowledge Base * Files are displayed with checkmarks when successfully uploaded * Use the cog icon to access advanced configuration options **Content Optimization** * Different content types work better with specific primary context settings * More specific search queries typically yield better results * Consider the chunking strategy based on your document types **Workflow Integration** * Content added to Knowledge Bases enhances AI capabilities by providing specialized context * Search results can be used as variables in subsequent workflow steps * Knowledge Bases persist across workflow runs, building institutional knowledge > πŸ’‘ **Think of it this way**: Knowledge Bases are like specialized libraries that your workflows can both contribute to and reference for better, more informed results. # Triggers Triggers are the starting points of any workflow in Lleverage. They determine how your workflow is initiated and what form it will take when published. Triggers define the entry point for your automat
Trigger Selection in Workflow studio

Trigger Selection

### Available Trigger Types * **App**: Creates user-facing applications (forms or chat interfaces) * **API Call**: Starts with a request from your application * **Schedule**: Runs on a recurring schedule or at specific times * **Integration**: Triggers based on events from external applications * **Data Table**: Runs when records change in a data table > πŸ’‘ You can have multiple triggers for multi-step workflows, but your primary trigger determines the publishing state of your workflow. > πŸ’‘ Subworkflows have their own trigger too: when you build a subworkflow, it starts from a subworkflow trigger that defines the inputs the parent workflow passes in. You don't add this from the trigger picker; it's created as part of the subworkflow itself. ### How to Add a Trigger 1. Open the canvas in the Workflow Studio 2. Locate the box that says "What starts this workflow? Select an action trigger" 3. Click on the box to see the available trigger options 4. Select your preferred trigger type (App, API Call, Schedule, Integration, or Data Table) 5. Configure the settings specific to your selected trigger ### How to Switch a Trigger 1. Look for the icon in the top right corner of your trigger action (arrows pointing right and left) 2. Click on this icon to open the trigger selection menu 3. Choose from the available trigger types to replace your current trigger 4. Configure your new trigger as needed > πŸ’‘ Switching triggers allows you to easily change how your workflow starts without rebuilding your entire automation.

Workflow Type Switching

### App Trigger β€” URL Parameters App triggers support **URL parameters** that let you pass input values directly through the app URL. This is useful for pre-filling forms, passing context from external systems (like an ERP or CRM), or creating dynamic links that customise the workflow for each user. #### How URL Parameters Work Parameters use **bracket notation** under the `i` namespace: ``` https://app.lleverage.ai//w/?i[fieldName]=value ``` For example, to pass a machine type and model: ``` https://app.lleverage.ai/xukfwbfwk/w/y8jbih5h?i[machine]=ficep&i[model]=coolaid ``` > πŸ’‘ Only parameters under the `i[...]` namespace are passed to the workflow. Other query parameters (e.g. analytics or tracking tags) are safely ignored. #### Accessing URL Parameters in Your Workflow URL parameters are available as an output of the App Trigger node: * **`urlParams`** β€” A key-value object containing all parameters passed via the URL You can reference these values in downstream nodes using expressions like `{{appTrigger.urlParams.machine}}`. #### Automatic Form Pre-filling When your workflow contains a **Form** node after the App Trigger, URL parameters are automatically matched to form fields by name. If a URL parameter key matches a form field name, that field's default value is set to the URL parameter value. **Example:** If your form has a field called `machine` and the URL contains `?i[machine]=ficep`, the form will pre-fill the machine field with "ficep" when the user opens the app. Key behaviours: * Parameters that match form field names are injected as defaults * Parameters that don't match any field are silently ignored * URL parameter values override any existing default values on the form schema * Values are treated as literal strings β€” template expressions in URL parameters are not evaluated (this prevents accidental data leaks) #### Multiple Parameters You can pass multiple parameters by chaining them with `&`: ``` ?i[machine]=ficep&i[model]=coolaid&i[notes]=urgent ``` #### Use Cases * **ERP integration**: Link directly from your ERP system with article numbers or order IDs pre-filled * **Custom links per client**: Generate unique URLs with client-specific defaults * **QR codes**: Encode parameters into QR code URLs for scanning in warehouse or factory settings * **Email campaigns**: Include pre-filled links in emails to streamline data entry > ⚠️ URL parameters are visible in the browser address bar. Do not pass sensitive information (passwords, API keys, secrets) through URL parameters. ### API Call Triggers API Call triggers allow your workflow to be initiated by external applications through API requests, enabling programmatic access to your automations. #### How to Configure an API Call Trigger 1. Select "API Call" as your trigger type 2. Click "Add Field" to create input parameters for your API 3. Enter field names and select appropriate data types 4. Under "Authentication," select either "Lleverage API Token" (recommended) or "None" > ⚠️ If you publish with Lleverage API Token enabled, you'll need to specify this in your embedded code using your organization's settings.

API Trigger

### Schedule Triggers Schedule triggers run your workflow automatically at specified times or intervals without any user interaction. #### How to Configure a Schedule Trigger 1. Select "Schedule" as your trigger type 2. Choose between "Specific Time" or "Intervals" 3. **For Specific Time:** * Set the hour and minute * Select AM or PM * Choose the date 4. **For Intervals, select a frequency:** * Every 5, 10, 15, or 30 minutes * Every 1, 2, 4, 6, or 12 hours > πŸ’‘ Scheduled triggers allow your workflow to run automatically without manual intervention.

Spcific Time Schedule

Intervall Time Schedule

### Integration Triggers Integration triggers start your workflow based on events from external applications, such as receiving an email or when a new file is added to a folder. #### How to Configure an Integration Trigger 1. Select "Integration" as your trigger type 2. In the "Search App" field, type or scroll to find your provider (e.g., Gmail) 3. Select the provider from the list 4. Choose an action that will trigger your workflow (e.g., "New Sent Email") 5. Complete the authentication by selecting "Online Authentication" 6. Configure any optional properties provided by the integration ### Data Table Triggers Data Table triggers start your workflow automatically when records change in one of your data tables, for example kicking off processing whenever a new order record is added. #### How to Configure a Data Table Trigger 1. Select "Data Table" as your trigger type 2. Choose the data table to watch 3. Pick which events should start the workflow: when records are **created**, **updated**, or **deleted**. You can select any combination. 4. Optionally add filters so the workflow only runs for records matching specific criteria The trigger provides the full record data, the event type, and the table information as outputs, so downstream actions can work with exactly what changed. > πŸ’‘ Combine a Data Table trigger with filters to react only to the records that matter, such as orders above a certain value. ### What Happens When You Publish Your choice of trigger determines what your workflow will become when published: * **App triggers** publish as standalone applications * **API Call triggers** publish as API endpoints * **Schedule triggers** publish as scheduled tasks * **Integration triggers** publish as integration-driven automations * **Data Table triggers** publish as automations that run when records change ### Key Features * Each trigger has a natural language description to help you understand its function * Triggers can be enabled or disabled to prevent unforeseen workflow runs * Easy switching between trigger types without rebuilding your workflow * Built-in variable creation for App and API Call triggers > ⚠️ Understanding variables is important when working with App and API Call triggers, as they create output variables that can be used throughout your workflow. > πŸ’‘ For detailed configuration of Form and Chat canvas actions, see the dedicated Form Actions and Chat Actions documentation pages. # Chat Chat actions are canvas actions that trigger a chat interface during workflow execution. Unlike App triggers that start with chat, Chat actions can be placed anywhere in your workflow to create conversational moments when needed. They're perfect for multi-step workflows where you need user interaction or clarification at specific points. ### How Chat Actions Work Chat actions create a pause in your workflow where: 1. The workflow reaches the Chat action 2. A chat interface appears to the user 3. The user can type messages and interact conversationally 4. The chat conversation creates variables that can be passed to subsequent actions 5. The workflow continues with the next action using the chat data ### How to Add a Chat Action 1. In your workflow canvas, click "Add Action" or use a connection circle 2. Search for "Chat" in the actions menu 3. Click on "Chat" to add it to your workflow 4. Position it where you want the conversational interaction to occur 5. Connect it to your previous and next actions ### Chat Action Configuration Chat actions are simple to configure: * No complex setup required * Automatically creates a chat interface when triggered * Generates chat variables for use in subsequent actions * Maintains conversation context during the interaction ### Multi-Step Workflow Integration Chat actions excel in multi-step workflows where you might: **Example Workflow Sequence:** 1. **Integration Trigger** - Workflow starts from an external event (e.g., new email received) 2. **Processing Actions** - Initial data processing or analysis 3. **Chat Action** - User interaction to gather additional information or provide updates 4. **Agent Action** - AI processes the chat conversation and previous workflow data 5. **Output Actions** - Final results or automated responses ### Chat Variables When a chat interaction completes: * Chat responses are captured in variables * These variables can be passed to subsequent actions * Variables contain the full conversation context * Can be used in Agents, Prompts, or any other workflow actions ### Use Cases for Chat Actions **Mid-Workflow Clarification:** * Integration triggers a workflow * Processing reveals missing information * Chat action requests clarification from user * Workflow continues with complete data **Human-in-the-Loop Processes:** * Automated analysis runs first * Chat action presents findings to user * User provides feedback or decisions * Agent processes the combined information **Progressive Information Gathering:** * Form collects initial data * Chat action allows natural follow-up questions * Multiple interaction points in single workflow ### Combining with Other Actions #### Chat + Agent Integration 1. Chat action collects user conversation 2. Agent action receives chat variables as input 3. Agent can process both chat context and other workflow data 4. Creates powerful AI-human collaboration #### Chat + Form Integration * Forms for structured data collection * Chat for flexible, conversational follow-ups * Combine structured and unstructured input in one workflow #### Chat + External Integrations * Integration triggers workflow * Chat action provides human oversight * Automated actions complete the process ### When to Use Chat Actions **Use Chat Actions when:** * You need user interaction mid-workflow * Clarification or human input is required at specific points * You want to combine automated processing with conversational elements * Multiple interaction types are needed in one workflow * You're building human-in-the-loop automations **Don't use Chat Actions when:** * You want to start a workflow with chat (use App trigger with Chat instead) * You need purely automated workflows without user interaction * Simple form input is sufficient ### Chat Action vs App Trigger with Chat **Chat Action (Mid-Workflow):** * Appears during workflow execution * Part of a larger automation sequence * Triggered by preceding workflow actions * Creates variables for subsequent actions **App Trigger with Chat:** * Starts the entire workflow * Primary interface for user interaction * Published as standalone chat application * User initiates the workflow through chat > πŸ’‘ Chat actions are perfect for creating interactive, multi-step workflows where human input enhances automated processing at key decision points. # Form Form actions are canvas actions that work with App triggers to create user-friendly data collection interfaces. When published, they become standalone form applications that anyone can use to submit information to your workflow. ### How to Configure a Form Action 1. Select "App" as your trigger type 2. Choose "Form" as your canvas action 3. Click "Add Field" to create a new input field 4. Enter the name of your field 5. Select the field type from the dropdown menu 6. Click "Create" to add the field to your form 7. Repeat steps 3-6 to add additional fields as needed > πŸ’‘ When you create a field, it automatically generates a variable chip that you can use to pass the output throughout your workflow. ### How to Edit Form Fields 1. Locate the field you want to edit on your form 2. Click the pencil icon next to the field 3. This opens the field configuration panel where you can modify: * **Variable Name**: The name used to pass data through the workflow * **Label**: The display name shown to users (defaults to variable name if not edited) * **Field-specific settings**: Varies by field type > ⚠️ If you delete the label, it will default to the variable name. You can add variables within labels. ### Available Field Types #### Text Field **Input Options:** * Single-line or multi-line text input * Multi-line option affects styling presentation **Configuration Options:** * Label * Default value * Placeholder text * Hint text * Minimum length * Maximum length * Multi-line toggle #### Number Field **Input Options:** * Standard input field * Slider input (can be checked/enabled) **Configuration Options:** * Required field toggle * Label * Default value * Placeholder text * Hint text * Minimum value * Maximum value #### Toggle Field **Input Options:** * Switch style * Checkbox style **Configuration Options:** * Required field toggle * Label * Default value (true or false) * Hint text #### Single Select Field **Input Options:** * Dropdown menu * Radio buttons **Configuration Options:** * Required field toggle * Label * Default value (dropdown selection) * Placeholder text * Hint text * Selection options (add and reorder options) #### Multi-Select Field **Input Options:** * Multiple selection interface **Configuration Options:** * Required field toggle * Label * Placeholder text * Hint text * Selection options (add and reorder options) #### Date Picker Field **Configuration Options:** * Label * Default value (year, month, day format) * Placeholder text * Hint text #### File Field **Configuration Options:** * Label * Placeholder text * Hint text * File type restrictions * File size limits #### Look Up Field **Configuration Options:** * Connects to external data sources * Dynamic field population * Search and selection capabilities #### Item List Field **Style Options:** * Card list display * Table display **Configuration Options:** * Required field toggle * Label * Hint text * Form structure for list items * Initial items (pre-populated entries) * Allow users to add more items toggle > πŸ’‘ The Item List field creates a table-like structure where users can add multiple entries with the same field structure. ### Field Validation and Requirements * **Required Fields**: Mark any field as required to prevent form submission until completed * **Field-specific Validation**: Each field type has appropriate validation (number format, file type, etc.) * **Length Limits**: Set minimum and maximum character limits for text fields * **Value Ranges**: Define minimum and maximum values for number fields * **Real-time Feedback**: Users receive immediate validation feedback ### Variable Creation and Usage * Each form field automatically creates a variable chip for use in subsequent workflow actions * Variable names can be customized in the field edit panel * Labels can include variables from other parts of your workflow * Form outputs are available throughout your entire workflow ### When to Use Form Actions **Use Form Actions when:** * You need structured data collection * Users should provide specific information in defined formats * You want to validate input fields before processing * The workflow requires multiple, organized data points * You need file uploads or complex data structures * You're collecting tabular data with Item Lists ### Publishing and Sharing When published with an App trigger: * Creates a standalone form application * Generates shareable links * Provides embed codes for integration * Works independently of the Lleverage platform * Can be customized with your branding * Responsive design works on all devices > πŸ’‘ Form actions create comprehensive variable outputs that make all collected data available to subsequent workflow actions, enabling powerful data processing and automation. # Output The Output action in Lleverage defines what information is returned from your workflow and signals when the workflow should end. Every workflow requires at least one Output action to function correctly, making it a crucial component of your automation design.

Output Action Card, adding varaibles

### Key Features * **Workflow completion indicator** that signals when processing should stop * **Return value definition** for specifying what data the workflow produces * **Support for multiple outputs** in multi-step workflows * **Variable integration** for dynamic output content * **Simple configuration** through a straightforward text box interface ### How to Add an Output Action 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one node to create a connection 2. Find the Output action in either: * The "All" tab * The "Tools" tab * The "Controls" subcategory 3. Look for a blue icon with a left-pointing arrow 4. Click on the Output action to add it to your canvas > ⚠️ Every workflow must have at least one Output action to function properly.
### How to Configure the Output Action 1. When you select the Output action, you'll see a simple text box 2. This text box allows you to specify what will be returned when the workflow ends 3. To include workflow variables: * Click in the text box to see the @ symbol at the bottom * Click the @ symbol to see available variables * Select the variable you want to include in the output > πŸ’‘ You can combine text and variables in the Output action to create formatted responses. ### How to Use Multiple Outputs 1. Each Output action has a plus (+) button on the right side of the action card 2. Clicking this button allows you to add additional output fields 3. Multiple outputs are useful for multi-step workflows where different paths may produce different results > ⚠️ In standard workflows, the Output action should typically be the final node without any connections leading out from it. ### Important Workflow Structure Considerations 1. Workflow Branching: * You cannot have one action connected to two different Output actions directly * Each distinct pathway in your workflow should have its own Output action * A valid structure would be: Trigger β†’ Actions β†’ Output, and separate Actions β†’ Output 2. Proper Workflow Structure: * For branching logic, use a Branch action first, then connect each branch to its own series of actions and an Output * A workflow with branches would follow this pattern: * Trigger β†’ Actions β†’ Branch β†’ Actions β†’ Output * And the other branch: Branch β†’ Different Actions β†’ Output > ⚠️ Attempting to connect one action card to multiple Output actions directly will not work, as this violates the workflow structure rules. ### How Output Actions Work in Your Workflow 1. Place the Output action at the end of your workflow 2. Configure what information should be returned when the workflow reaches this point 3. When the workflow execution reaches an Output action, it will: * Return the specified information * Stop processing that branch of the workflow * Consider that pathway complete > πŸ’‘ Think of Output actions as the "exit points" of your workflow that determine what information is provided back to the user or system that triggered it. ### Example Output Scenarios #### Single Output Workflow 1. Trigger β†’ Action β†’ Action β†’ Output 2. The workflow processes linearly and returns one result #### Multi-Step Workflow with Multiple Outputs 1. Trigger β†’ Actions β†’ Branch (based on condition) 2. If condition is true: Branch β†’ Actions β†’ Output A 3. If condition is false: Branch β†’ Different Actions β†’ Output B 4. The workflow returns different results depending on which path was taken > πŸ’‘ Using multiple outputs allows your workflow to provide different responses based on conditions, inputs, or processing results. # Agent An Agent action in Leverage allows you to create AI-powered automation that can perform multiple steps and make decisions to complete complex tasks. Agents use the actions you provide to work through problems autonomously until the specified objective is achieved. ### Key Features * Decision-making capabilities to determine the best approach to a task * Action selection from tools you provide * Iterative processing that continues until instructions are fulfilled * Dynamic variable integration for workflow context * Ability to process files and access knowledge bases * Smart suggestions for improving agent configuration ### How to Add an Agent Action 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Select "AI" from the categories or find "Agent" in the options 3. Click on "Agent" to add it to your canvas > πŸ’‘ The Agent action appears similar to the Prompt action in the workflow canvas
### How to Add an Agent Action 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Select "AI" from the categories or find "Agent" in the options 3. Click on "Agent" to add it to your canvas > πŸ’‘ The Agent action appears similar to the Prompt action in the workflow canvas. ### How to Configure the Agent Action Card 1. Locate the Agent card on your canvas which includes: * Header with the action name * Variable chip in the top left corner for referencing outputs * Control buttons for expanding/collapsing and running the agent * Connection points for inputs and outputs 2. Configure the basic settings: * **Instructions**: Add your agent's objective in the instructions box 3. Provide clear instructions for what the agent needs to accomplish > ⚠️ Be specific with instructions as this determines how the agent will operate. #### Expanding the Instructions View To view your instructions in a larger format: * Hover over the input box at the bottom right corner * Click the expand arrows icon * This opens an expanded view for easier editing of longer instructions ### How to Add Actions and Resources to Your Agent Below the instructions section, you can add various resources by clicking the "+" button: #### 1. Add an App * Integrates external applications like Gmail, Slack, Outlook, and other services * Provides access to Leverage's built-in tools and integrations #### 2. Add an Action * Select from Leverage's action library * Configure action parameters or leave them blank for the agent to determine * For sub-actions, you can specify parameters if needed or let the agent fill them out automatically #### 3. Add a Variable * Reference workflow variables the agent should use * Ensures the agent has access to necessary data from previous steps #### 4. Add a Knowledge Base * Select from your available knowledge bases * Gives the agent access to specific information repositories > πŸ’‘ The agent will attempt to automatically configure actions when possible, using context from your instructions. ### How to Configure JSON Output Format When you add an action to your agent, you can configure structured JSON output: **How to Set Up JSON Output** 1. After adding an action to your agent, look for the "Advanced" section 2. Select "JSON Output" option 3. Configure the schema using one of two methods: **Simple Table Method:** 1. Use the simple table interface 2. Add attributes by specifying field names and types 3. Define the structure using the visual editor **Advanced JSON Schema:** 1. Switch to the "Advanced" section 2. Write the JSON schema directly 3. Define the exact structure and validation rules you want This allows you to ensure the agent returns data in a specific, structured format that can be easily used by subsequent workflow actions. > πŸ’‘ JSON output configuration helps maintain consistent data structure across your workflow ### Agent Suggestions Feature Below the agent card, you'll find a suggestions panel that provides: 1. **Action Recommendations**: Suggests relevant actions based on your instructions 2. **Variable Recommendations**: Identifies variables that might be useful for your task 3. **Instruction Formatting**: If your instructions aren't optimally structured, a magic wand icon appears * Click the magic wand to automatically reformat your prompt * This creates a more systematic structure that agents can better understand ### How the Agent Action Works 1. The agent analyzes your instructions to understand the objective 2. It selects appropriate actions from those you've provided 3. It executes actions in sequence, making decisions based on results 4. The process continues until the agent determines the instructions have been fulfilled 5. The final output is passed to the next action in your workflow > ⚠️ If action configurations have been previously specified in your workflow, the agent will follow those rules rather than creating its own configuration. ### How the Agent Action Works 1. The agent analyzes your instructions to understand the objective 2. It selects appropriate actions from those you've provided 3. It executes actions in sequence, making decisions based on results 4. The process continues until the agent determines the instructions have been fulfilled 5. The final output is passed to the next action in your workflow > ⚠️ If action configurations have been previously specified in your workflow, the agent will follow those rules rather than creating its own configuration ### Writing Effective Agent Instructions #### Structure Guidelines 1. **Clear Objective**: Start with a specific goal statement 2. **Context**: Provide relevant background information 3. **Constraints**: Specify any limitations or requirements 4. **Expected Output**: Describe what success looks like #### Best Practices * Be clear about the specific goal the agent needs to achieve * Specify any constraints or requirements for the solution * Reference any variables the agent should use with proper syntax * Focus on the "what" (goal) rather than the "how" (specific steps) * Use the formatting suggestions when available to improve clarity * Start with action verbs: "Research," "Analyze," "Create," "Process" * Define success criteria clearly * Explain the business context or use case * Include relevant details about the data or situation * Set boundaries for the agent's actions * Define quality standards or formatting requirements * Use clear, concise language * Break complex objectives into logical components * Avoid ambiguous terms or jargon > πŸ’‘ For best results, provide context that helps the agent understand the problem scope #### Example Instruction Formats **For Research Tasks:** ``` Research and analyze [specific topic] using the provided knowledge base and web search capabilities. Focus on [specific aspects] and compile findings into a comprehensive summary that includes key insights, trends, and actionable recommendations. Ensure all sources are properly cited. ``` **For Data Processing:** ``` Process the uploaded customer data to identify patterns in purchasing behavior. Analyze the data for trends, segment customers by behavior type, and generate a report with visualizations showing key insights. Use the customer database for additional context where needed. ``` **For Content Creation:** ``` Create a professional email campaign based on the provided customer segment data. The email should be personalized, follow our brand guidelines from the knowledge base, and include compelling subject lines. Generate 3 variations for A/B testing purposes. ``` #### Advanced Techniques **Use Conditional Logic:** * "If X condition is met, then Y action should be taken" * "When analyzing data, prioritize recent entries over historical ones" * "In case of missing information, use the knowledge base to fill gaps" **Specify Output Format:** * "Present findings in a structured report with executive summary, detailed analysis, and recommendations" * "Output results as a JSON object with specific field names" * "Create a markdown-formatted document with proper headers and sections" **Include Quality Checks:** * "Verify all calculations before presenting results" * "Cross-reference findings with multiple sources when possible" * "Flag any inconsistencies or potential issues in the data" > ⚠️ Avoid being too vague about the desired outcome or providing step-by-step instructions instead of objectives > πŸ’‘ Use the formatting suggestions feature when available to automatically optimize your instruction structure ### Working with Files and Data Agents can: * Process files passed through triggers * Access information from connected knowledge bases * Handle multiple data sources simultaneously * Pass processed information to subsequent workflow steps ### Testing Your Agent Action **How to test your agent:** 1. Click the "Run" button on the Agent card to test it with current workflow variables 2. Review the final output to ensure it meets your requirements 3. If the agent encounters issues: * The output panel will explain why it couldn't complete the task * Review the error message for guidance on adjustments needed * Adjust instructions or available actions if necessary to improve results > ⚠️ Agents may take longer to execute than standard prompts because they perform multiple steps to complete a task ### Troubleshooting If your agent isn't performing as expected: 1. Check the output panel for detailed error messages 2. Ensure all necessary actions and resources are added 3. Use the suggestion feature to optimize your instructions 4. Verify that variables are correctly referenced 5. Consider breaking complex tasks into smaller, clearer objectives 6. Review your instructions for clarity and specificity 7. Test with simpler objectives first to validate the agent setup # AI AI Tools in Lleverage provide powerful artificial intelligence capabilities to enhance your workflows. These tools allow you to leverage AI for text generation, web searching, image creation, and intelligent automation without managing API keys or complex configurations. ### Key Features * Natural language instructions for directing AI behavior * Multiple model options to optimize for balance, speed, or intelligence * Variable integration for dynamic workflow data * Support for text, images, and files as input * Advanced configuration options through specialized interfaces > πŸ’‘ **Tip:** All AI tools support variable integration, allowing you to create dynamic, data-driven automations that adapt to your workflow inputs. ### Available AI Tools #### Prompt Give instructions to AI models for text processing and generation. The core mechanic that drives AI features in your automations with support for chat completions and text analysis. #### Agent Create autonomous AI that can perform multi-step tasks and make decisions. Agents use the actions you provide to work through problems until the specified objective is achieved. #### AI Web Search Search the internet and get AI-powered answers. Combines real-time web searching with intelligent answer generation for comprehensive, contextual responses. #### Generate Image Create custom images from text descriptions. AI-powered image generation that produces high-quality visual content based on your prompts. #### Browser Agent Automate web browser interactions with AI. Navigate websites, click through processes, and complete tasks just like a human user would, then return the results to your workflow. > ⚠️ **Premium Feature:** Browser Agent is only available on Pro and Enterprise plans. This feature is not included in free accounts. ### Getting Started To add any AI tool to your workflow: 1. Click the "Add Action" button or connection circle 2. Select "AI" from the categories or find the specific tool in "Tools" tab 3. Click on your desired AI tool to add it to the canvas 4. Configure the tool with your instructions and variables > ⚠️ **Warning:** Different models have different capabilities and processing speeds. Choose the model that best fits your workflow's needs for balance, speed, or intelligence. *** ## Browser Agent **Browser Agent** is an AI-powered node that automates web browser interactions. It can navigate websites, click through processes, and complete tasks just like a human user would, then return the results to your workflow. ### Key Features * AI-powered web browser automation * Real-time interaction with websites * Human-like navigation and clicking * Task completion with intelligent problem-solving * Recording playback of browser sessions * Session viewing capabilities ### How to Add a Browser Agent Action 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to the **Tools** tab in the action menu 3. Find the **AI** subcategory under Tools 4. Click on **Browser Agent** to add it to your canvas > πŸ’‘ **Tip:** Browser Agent actions will be automatically numbered if you add multiple instances (Browser Agent 1, Browser Agent 2, etc.) ### How to Configure the Browser Agent Action Card 1. Locate the Browser Agent card on your canvas which includes: * Header with the action name (which can be renamed) * Variable chip in the top left corner for referencing outputs * Controls for expanding/collapsing, running the agent, and additional options * Connection points for inputs and outputs 2. Configure the **Task** input field: * Describe what you want the browser agent to accomplish * Be specific about the website and actions you want performed * Use clear, step-by-step language for complex tasks 3. The AI will interpret your task and execute the browser interactions automatically ### How to Write Effective Browser Agent Tasks 1. **Be specific about the target website**: * Example: "Go to leverage.ai and describe what Lleverage does" * Example: "Navigate to Amazon.com and search for wireless headphones" 2. **Describe the desired outcome clearly**: * What information you want extracted * What actions should be completed * What format you want the results in 3. **Use action-oriented language**: * "Go to \[website]" * "Click on \[element]" * "Search for \[term]" * "Extract \[information]" * "Fill out \[form]" 4. **Combine multiple steps in one task**: * Example: "Go to LinkedIn, search for companies in the tech industry, and list the top 5 results" ### How to Run and Monitor Browser Agent Tasks 1. Click the play button on the Browser Agent action card to start execution 2. **Be patient during execution**: * Browser Agent tasks take longer than typical AI actions * The agent works in real-time, simulating human interactions * Processing time varies based on task complexity 3. **Monitor the progress**: * The agent will work through each step systematically * It can handle unexpected situations and adapt as needed * Some complex interactions may require additional processing time > ⚠️ **Warning:** Browser Agent tasks can take significantly longer than other workflow actions due to real-time web interaction requirements. ### How to Review Browser Agent Results 1. **View the Output**: * The agent will return the requested information or confirmation of completed actions * Results appear in the standard output format for use in subsequent workflow steps 2. **Access Session Recording**: * After execution, two new buttons appear on the Browser Agent card: * **View Recording** - Opens a popup showing the step-by-step browser interactions * **Open Session** - Opens the browser session in a new window for review 3. **Analyze the Process**: * Use the recording to understand how the agent navigated the task * Review tab structure and interaction patterns * Identify any areas for task optimization ### Best Practices * **Start with simple tasks** to understand how the agent interprets instructions * **Be explicit about required information** to ensure accurate extraction * **Test tasks thoroughly** before deploying in production workflows * **Use clear, unambiguous language** in task descriptions * **Consider timeout implications** for time-sensitive workflows * **Review recordings** to optimize future task descriptions ### Troubleshooting * **If the agent gets stuck**: Review your task description for clarity and specificity * **For failed executions**: Check the session recording to identify where issues occurred * **For slow performance**: Consider breaking complex tasks into smaller, focused steps * **For unexpected results**: Refine your task instructions with more specific requirements ### Output Format The Browser Agent action outputs: * Extracted information or data as requested in the task * Confirmation of completed actions * Structured results ready for use in subsequent workflow steps * Access to session recordings for process review > πŸ’‘ **Tip:** Browser Agent results can be used as variables in other workflow actions, making it perfect for automated data collection, form filling, and web-based research tasks. # Prompt A Prompt in Lleverage is a concise set of instructions in natural language that guides AI models to perform specific tasks within your workflow. Prompts are the core mechanic that drives the features you're building in your automations. ### Key Features * **Natural language instructions** for directing AI behavior * **Multiple model options** to optimize for balance, speed, or intelligence * **Support for text, images, and files** as input for processing * **Variable integration** for dynamic workflow data * **Advanced configuration** through Prompt Studio ### How to Add a Prompt Action 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Select "AI" from the categories or find "Prompt" in the "All" tab 3. Click on "Prompt" to add it to your canvas > πŸ’‘ If you add multiple prompts, they will be automatically numbered (Prompt 1, Prompt 2, etc.) ### How to Configure the Prompt Action Card 1. Locate the Prompt card on your canvas which includes: * Header with the action name (which can be renamed) * Variable chip in the top left corner for referencing outputs * Controls for expanding/collapsing, running the prompt, and additional options * Connection points for inputs and outputs * Natural language description that updates automatically 2. Configure basic settings directly on the card: * **Model selection**: Choose from Balanced (default), Fastest, or Smartest options * **Instructions**: Add up to three instruction blocks in the main card view 3. Set up your instructions: * Type your prompt text in the instructions area * Specify message roles (user or assistant) if desired * Generate content by clicking the star icon in the bottom left * Add media references using the image or clip icons > ⚠️ Different models have different capabilities and speed. The model you choose may affect whether text, image, audio, and PDF processing are available.

Basic Prompt Action

### How to Add Media and Files to Prompts 1. Click the image icon or clip icon in the instruction area 2. A link field will appear below the instruction 3. Enter a variable reference, image URL, or file reference in this field 4. Delete media attachments by clicking the delete icon if needed

Adding an image within a Prompt Action

### Improved File Support **Gamechanger alert!** Prompt node attachments can now include files of different types across all models! Using MarkItDown we support the conversion into markdown from: * **PDF** - Full text extraction and formatting * **PowerPoint** - Slide content and notes * **Word** - Document text and formatting * **Excel** - Spreadsheet data and structure * **Images** - EXIF metadata and OCR text extraction * **Audio** - EXIF metadata and speech transcription * **HTML** - Web page content * **Text-based formats** - CSV, JSON, XML * **ZIP files** - Iterates over contents * **YouTube URLs** - Video transcripts and metadata * **EPubs** - E-book content πŸ’‘ Files are automatically converted to markdown format for optimal AI processing, preserving structure and content while making it accessible to the language models. ### How to Write Effective Prompts 1. Be specific with your instructions to ensure relevant responses 2. Provide clear context to help the model produce accurate results 3. Structure your prompt logically 4. Consider using: * Dynamic variables with the '@' button or typing with `{{ brackets }}` syntax for real-time data insertion * Parameters, traits, and constraints to guide the AI response * Different message roles to structure conversations > πŸ’‘ You can reorder multiple instructions using the grab handles on the right side of each instruction box. ### How to Access Prompt Studio (formerly Prompt IDE) 1. Add a Prompt action to your workflow canvas 2. Click on "Prompt Studio" at the bottom of the Prompt card 3. The full-screen Prompt Studio interface will open > πŸ’‘ You can move back and forth between Prompt Studio and your workflow for the most effective experience.

Prompt Studio

Prompt Node Footer and link to Prompt Studio

### How to Use Prompt Studio In the expanded Prompt Studio view, you can: * Select your model from expanded options * Configure advanced model settings (temperature, top P, top K, max tokens) * Set output format (text or JSON with optional schema) * Resize columns for better workspace management * Add and reorder multiple instructions using grab handles Advanced configuration includes: * **Output settings**: Choose between text or JSON format with schema options * **Column resizing**: Adjust the workspace to focus on different aspects of prompt building * **Expanded instruction view**: More space for complex prompt engineering > ⚠️ Advanced model settings like temperature and token limits should only be adjusted if you understand their impact on AI behavior ### How to Configure Advanced Model Settings 1. In Prompt Studio, locate the cog button on the right side of the model selection 2. Click the cog button to open advanced configuration options 3. Configure the following parameters as needed: * **Temperature**: Controls randomness in responses * **Top P**: Nucleus sampling parameter * **Top K**: Top-k sampling parameter * **Frequency Penalty**: Reduces repetition of tokens * **Presence Penalty**: Encourages topic diversity * **Max Tokens**: Maximum response length ### How to Set Output Format 1. In the advanced settings, locate the "Format" section 2. Choose between two options: * **Text**: Output will be returned as plain text * **JSON**: Output will be structured as JSON data **For JSON Output:** 1. Select "JSON" from the format options 2. Toggle "JSON Schema" to enable schema definition 3. Enter your desired JSON schema in the provided field 4. This ensures the AI returns data in the exact structure you specify > πŸ’‘ JSON output with schema is particularly useful when you need structured data for subsequent workflow actions ### How to Test Prompts in Prompt Studio 1. Locate the "Test with mock data" option in the top right corner 2. This allows you to test the prompt in isolation from the rest of the workflow 3. Fill in any required variables with test values 4. Click "Run" to see the AI's response 5. Make adjustments based on the results > πŸ’‘ Testing with mock data lets you isolate and perfect your prompt before integrating it with the full workflow ### How to Create and Compare Variants 1. In Prompt Studio, click the chevron next to your variant name in the left column 2. Select "Add new variant" to create a new version 3. Configure the new variant with different settings or instructions **To compare variants:** 1. Click "Compare mode" 2. View variants side-by-side in vertical format 3. See how each responds to the same input 4. Create new variants directly from comparison view 5. Duplicate variants as needed 6. Activate your preferred variant by selecting it and returning to edit mode > πŸ’‘ Creating variants allows you to keep your previous configurations while testing new approaches ### How to Save and Exit 1. All changes are automatically saved when you close Prompt Studio 2. Click the X or close button to return to the workflow canvas 3. Your prompt configurations will be processed and integrated with your workflow ### Types of Prompts Supported * **Chat** for conversational flows * **Completions** for text analysis, text generation, or data processing # AI Web Search **AI Web Search** is an AI-powered node that combines internet searching with intelligent answer generation. It searches the web for relevant information based on your query and uses AI to provide comprehensive, contextual answers within your workflow. ### Key Features * Real-time web searching capabilities * AI-powered answer generation from search results * Variable integration for dynamic queries * Simple query-based interface * Automatic processing of search results into useful responses

AI Web Search Action

### How to Add an AI Web Search Action 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Find "AI Web Search" in the "All" tab or under the AI Tools category 3. Click on "AI Web Search" to add it to your canvas > πŸ’‘ **Tip:** If you add multiple AI Web Search actions, they will be automatically numbered (AI Web Search 1, AI Web Search 2, etc.) ### How to Configure the AI Web Search Action Card 1. Locate the AI Web Search card on your canvas which includes: * Header with the action name (which can be renamed) * Variable chip in the top left corner for referencing outputs * Controls for expanding/collapsing, running the search, and additional options * Connection points for inputs and outputs 2. Configure the search query in the main input field: * Type your search query directly as free text * Use variables by clicking the '@' button to insert dynamic data * Combine variables with static text for more specific searches 3. The AI will automatically process search results and generate intelligent answers ### How to Write Effective Search Queries 1. **Be specific with your search terms** to get more relevant results 2. **Use clear, descriptive language** that matches what you're looking for 3. **Combine variables with context** for dynamic searches: * Example: "Latest news about {{company\_name}} financial performance" * Example: "Best practices for {{industry}} in 2025" 4. **Consider the scope of your search**: * Broad queries for general information * Specific queries for detailed answers > πŸ’‘ **Tip:** The Web Search node works best when your query clearly defines what type of information you're seeking. ### How to Use Variables in Search Queries 1. **Using the '@' button method**: * Click in the query field to see the '@' symbol appear * Click '@' to open the variables panel * Select the variable you want to include from the list 2. **Using the advanced method**: * Type two curly braces `{{` in the query field * Begin typing the node name to see autocomplete options * Select the specific output you want to reference 3. **Combining variables with text**: * Mix variables with static text for context * Example: "Find competitor analysis for {{user\_input}} industry" ### How to Test Your AI Web Search 1. Click the play button on the AI Web Search action card to run a test 2. If using variables, ensure connected nodes have been run first to provide data 3. Review the AI-generated response to ensure it meets your needs 4. Adjust your query if the results aren't what you expected > ⚠️ **Warning:** AI Web Search requires an active internet connection and may take longer than other AI actions due to the search and processing steps. ### Best Practices * **Keep queries focused** - specific questions get better answers * **Use variables strategically** to make searches dynamic and relevant * **Test with different query formats** to find what works best for your use case * **Consider the context** of where this search fits in your overall workflow ### Output Format The AI Web Search action outputs: * AI-generated answer based on search results * Relevant information synthesized from multiple sources * Contextual response tailored to your query > πŸ’‘ **Tip:** The AI Web Search output can be used as input for other actions in your workflow, making it perfect for research-based automations. # Generate Image **Generate Image** is an AI-powered node that creates images based on your text descriptions. Simply provide a prompt describing what you want to see, and the AI will generate a custom image for your workflow. ### Key Features * AI-powered image generation from text descriptions * Variable integration for dynamic image creation * Simple prompt-based interface * High-quality image output * Seamless integration with workflow data

Generate Image Action

### How to Add a Generate Image Action 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Find "Generate Image" in the "All" tab 3. Click on "Generate Image" to add it to your canvas > πŸ’‘ **Tip:** If you add multiple Generate Image actions, they will be automatically numbered (Generate Image 1, Generate Image 2, etc.) ### How to Configure the Generate Image Action Card 1. Locate the Generate Image card on your canvas which includes: * Header with the action name (which can be renamed) * Variable chip in the top left corner for referencing outputs * Controls for expanding/collapsing, running the generation, and additional options * Connection points for inputs and outputs 2. Configure the **Prompt** input field: * Type your image description directly as free text * Use variables by clicking the '@' button to insert dynamic data * Combine variables with static text for more specific image descriptions 3. The AI will automatically generate an image based on your prompt ### How to Write Effective Image Prompts 1. **Be descriptive and specific** about what you want to see: * Example: "A professional headshot of a person in business attire" * Example: "A modern office space with natural lighting and plants" 2. **Include important details** like: * Style (realistic, cartoon, artistic, etc.) * Colors and lighting * Setting or background * Mood or atmosphere 3. **Use clear, visual language** that helps the AI understand your vision 4. **Combine variables for dynamic content**: * Example: "A product photo of {{product\_name}} on a white background" * Example: "An illustration showing {{user\_concept}} in a modern style" ### How to Use Variables in Image Prompts 1. **Using the '@' button method**: * Click in the prompt field to see the '@' symbol appear * Click '@' to open the variables panel * Select the variable you want to include from the list 2. **Using the advanced method**: * Type two curly braces `{{` in the prompt field * Begin typing the node name to see autocomplete options * Select the specific output you want to reference 3. **Combining variables with descriptive text**: * Mix variables with static descriptions for context * Example: "Create a logo for {{company\_name}} using blue and white colors" ### How to Test Your Generate Image Action 1. Click the play button on the Generate Image action card to run a test 2. If using variables, ensure connected nodes have been run first to provide data 3. Review the generated image to see if it matches your expectations 4. Adjust your prompt if the image doesn't meet your requirements > ⚠️ **Warning:** Image generation may take longer than other AI actions due to the processing complexity involved. ### Best Practices * **Be specific with your descriptions** - detailed prompts create better images * **Use variables strategically** to create dynamic, personalized images * **Test different prompt styles** to find what works best for your use case * **Consider the context** of how the image will be used in your workflow * **Include style and quality descriptors** for more professional results ### Output Format The Generate Image action outputs: * A high-quality generated image based on your prompt * Image file that can be used in other workflow actions * Visual content ready for sharing or further processing > πŸ’‘ **Tip:** Generated images can be used as inputs for other actions in your workflow, making them perfect for creating dynamic visual content for reports, presentations, or communications. # Evaluate The Evaluate node enables you to validate outcomes, perform safety checks, and add content moderation to your AI workflows. You can add multiple evaluations per node, with flexible configuration options and branching based on pass/fail status. ### Key Features * AI-powered content analysis and validation * Multiple evaluation types: Prompt, Expression, and Function * Pre-built presets for common safety and quality checks * Configurable fail/flag triggers for workflow routing * Support for multiple evaluations per node ### How to Add an Evaluate Node 1. Open your workflow in the workflow builder 2. Click the "Add Action" button 3. Navigate to the "AI" category 4. Select "Evaluate" 5. The node will be added to your canvas ### Evaluation Types When you add an evaluation, you first select the type. There are three types available: #### Prompt Evaluation AI-powered content analysis using LLM classification. 1. Click "Add Evaluation" 2. Select "Prompt" as the type 3. Choose a preset or select "Custom" to write your own instruction 4. Specify the variables to evaluate 5. Configure the fail trigger (Fail or Flag) 6. Set additional configuration: * Select the model * Set the confidence threshold * Add a title and description 7. Click "Add Evaluation" #### Expression Evaluation Logic-based validation using expressions that evaluate to boolean. 1. Click "Add Evaluation" 2. Select "Expression" as the type 3. Enter your JSON expression 4. Configure the fail trigger (Fail or Flag) 5. Add a title and description 6. Click "Add Evaluation" #### Function Evaluation Custom code-based validation for complex logic. 1. Click "Add Evaluation" 2. Select "Function" as the type 3. Write your evaluation code 4. Configure the fail trigger (Fail or Flag) 5. Add a title and description 6. Click "Add Evaluation" ### Available Presets When using Prompt evaluations, you can choose from the following presets: | Preset | Description | | ------------------- | ---------------------------------------------------------------------- | | Jailbreak Detection | Detects prompt injection and jailbreak attempts | | NSFW Text | Detects sexual content, hate speech, violence, inappropriate material | | Politeness | Checks if content maintains professional/polite tone | | Contains PII | Detects personally identifiable information (names, emails, SSN, etc.) | | Profanity Free | Checks for profanity or offensive language | | Ground Truth | Validates response against provided ground truth/context | | Factual Accuracy | Checks for potential hallucinations or unsupported claims | | Brand Safety | Detects content that could harm brand reputation | | Toxicity | Detects toxic, harmful, or abusive language | | Off-Topic | Checks if response stays on topic relative to the query | | Sentiment | Analyzes sentiment (can be configured for positive/negative/neutral) | | Language Detection | Ensures content is in expected language(s) | | Competitor Mention | Detects mentions of competitor brands/products | | Legal Compliance | Flags potentially legally problematic content | | Non-Empty Response | Validates that a response is not empty | | Max/Min Length | Checks response length is within bounds | | Valid JSON | Validates that output is valid JSON | | Valid URL | Validates that output contains valid URLs | | Valid Email | Validates that output contains valid email addresses | | Number Range | Checks that numeric values fall within a specified range | ### Fail Triggers Each evaluation has a fail trigger that determines what happens when the evaluation is triggered: * **Fail**: Routes the workflow to the fail edge (blocking) * **Flag**: Continues workflow execution but marks the evaluation as flagged (non-blocking) ### How to Manage Evaluations Once you've added evaluations to your node, you can: * **Edit**: Click on an evaluation to modify its configuration * **Remove**: Click the trash icon on an evaluation to delete it * **Reorder**: Drag evaluations to change their order πŸ’‘ You can add multiple evaluations to a single Evaluate node. All evaluations run in parallel. ### Node Edges The Evaluate node has two edges: * **Pass edge (top)**: Continues workflow execution when all evaluations pass, or when evaluations with flag action trigger (non-blocking) * **Fail edge (bottom)**: Routes execution when any evaluation with fail action triggers ### Activity View In the Activity view, you can see the evaluation status for each workflow run: | Status | Icon | Description | | ------ | --------- | ---------------------------------------------- | | Pass | βœ“ (Green) | All evaluations passed | | Flag | βš‘ (Amber) | One or more evaluations flagged (non-blocking) | | Fail | βœ• (Red) | One or more evaluations failed (blocking) | ### Best Practices * Use descriptive titles and descriptions for your evaluations to improve traceability * Start with presets for common use cases, then customise as needed * Use "Flag" for quality monitoring and "Fail" for critical safety checks * Combine multiple evaluations to create comprehensive validation pipelines * Review flagged items in the Activity view to identify patterns and improve your workflows # Categorise The Categorize node is an AI-powered action that classifies input into predefined categories. It automatically routes your workflow based on the classification, allowing you to create branching logic based on the type of content received. ### Key Features * AI-powered content classification * Pre-built templates for common categorization use cases * Automatic workflow branching based on category * Configurable model and additional context * Support for custom categories with titles and descriptions ### How to Add a Categorize Node 1. Open your workflow in the workflow builder 2. Click the "Add Action" button 3. Navigate to the "AI" category 4. Select "Categorize" 5. The node will be added to your canvas ### How to Configure Categorize #### Step 1: Add Your Input 1. Add the variable you want to categorize 2. This is the content that the AI will analyse to determine the category #### Step 2: Select a Template or Create Custom Categories Choose a preset template to get started quickly, or create your own custom categories. **Available Templates:** | Template | Description | | ---------------------- | --------------------------------------------------- | | Custom | Empty template for user-defined categories | | Order Categorisation | New Order, Modification, Cancellation, Return | | Invoice Categorisation | Utilities, Software, Travel, Supplies | | Chat Intent Routing | Route based on user intent in conversations | | Prize Categorisation | Categorize prize-related content | | Support Triage | Bug Report, Feature Request, Account Issue, General | | Email Categorisation | Sales Lead, Support, Partnership, Spam | πŸ’‘ Selecting a template populates the categories with predefined names and descriptions. You can modify these after selecting. #### Step 3: Add Categories If using custom categories or modifying a template: 1. Click "Add Category" 2. Enter a title for the category 3. Enter a description explaining what content belongs in this category 4. Repeat for each category you need πŸ’‘ Write clear, detailed descriptions for each category. This helps the AI make accurate classifications. #### Step 4: Configure Advanced Settings (Optional) Click on Advanced Configuration to access: * **Model**: Select which AI model to use for classification * **Additional Context**: Provide extra context to help the AI make better decisions ### How Branching Works The Categorize node works as a branching router in your workflow: * **Top connector**: The normal flow connector for incoming connections * **Category branches**: Each category you create has its own output connector When the node runs: 1. The AI analyses the input content 2. It selects the most appropriate category 3. The workflow continues down the branch for that category If the content doesn't match any category, it continues through the normal route. ### How to Edit Categories 1. Click on an existing category in the node 2. Modify the title or description 3. Save your changes To remove a category, click the trash icon next to it. ### Example Use Cases #### Support Ticket Routing **Categories:** * Bug Report β†’ Route to Engineering team * Feature Request β†’ Route to Product team * Account Issue β†’ Route to Support team * General Inquiry β†’ Route to Help desk #### Email Triage **Categories:** * Sales Lead β†’ Add to CRM * Support Request β†’ Create support ticket * Partnership Inquiry β†’ Forward to partnerships team * Spam β†’ Archive #### Invoice Processing **Categories:** * Utilities β†’ Tag as operational expense * Software β†’ Tag as technology expense * Travel β†’ Tag as travel expense * Supplies β†’ Tag as office expense ### Best Practices #### Writing Good Category Descriptions ❌ **Bad:** "Problems" βœ… **Good:** "Technical issues like crashes, errors, or broken features that prevent normal use of the product" ❌ **Bad:** "Questions" βœ… **Good:** "General inquiries about product usage, pricing, availability, or how-to questions" #### Tips for Effective Categorization * Be specific and detailed in your descriptions * Include examples in descriptions where helpful * Make categories mutually exclusive to avoid confusion * Avoid ambiguous or overlapping categories * Use 2-20 categories for best results * Test with sample inputs to verify accuracy ### Limits | Setting | Limit | | --------------------------- | -------------- | | Minimum categories | 2 | | Maximum categories | 20 | | Category title length | 50 characters | | Category description length | 500 characters | # Browser Agent **Browser Agent** is an AI-powered node that automates web browser interactions. It can navigate websites, click through processes, and complete tasks just like a human user would, then return the results to your workflow. > ⚠️ **Premium Feature:** Browser Agent is only available on Pro and Enterprise plans. This feature is not included in free accounts.

Successfully Ran Browser Agent Action

### Key Features * AI-powered web browser automation * Real-time interaction with websites * Human-like navigation and clicking * Task completion with intelligent problem-solving * Recording playback of browser sessions * Session viewing capabilities ### How to Add a Browser Agent Action 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to the **Tools** tab in the action menu 3. Find the **AI** subcategory under Tools 4. Click on **Browser Agent** to add it to your canvas > πŸ’‘ **Tip:** Browser Agent actions will be automatically numbered if you add multiple instances (Browser Agent 1, Browser Agent 2, etc.) ### How to Configure the Browser Agent Action Card 1. Locate the Browser Agent card on your canvas which includes: * Header with the action name (which can be renamed) * Variable chip in the top left corner for referencing outputs * Controls for expanding/collapsing, running the agent, and additional options * Connection points for inputs and outputs 2. Configure the **Task** input field: * Describe what you want the browser agent to accomplish * Be specific about the website and actions you want performed * Use clear, step-by-step language for complex tasks 3. The AI will interpret your task and execute the browser interactions automatically ### How to Write Effective Browser Agent Tasks 1. **Be specific about the target website**: * Example: "Go to leverage.ai and describe what Lleverage does" * Example: "Navigate to Amazon.com and search for wireless headphones" 2. **Describe the desired outcome clearly**: * What information you want extracted * What actions should be completed * What format you want the results in 3. **Use action-oriented language**: * "Go to \[website]" * "Click on \[element]" * "Search for \[term]" * "Extract \[information]" * "Fill out \[form]" 4. **Combine multiple steps in one task**: * Example: "Go to LinkedIn, search for companies in the tech industry, and list the top 5 results" ### How to Run and Monitor Browser Agent Tasks 1. Click the play button on the Browser Agent action card to start execution 2. **Be patient during execution**: * Browser Agent tasks take longer than typical AI actions * The agent works in real-time, simulating human interactions * Processing time varies based on task complexity 3. **Monitor the progress**: * The agent will work through each step systematically * It can handle unexpected situations and adapt as needed * Some complex interactions may require additional processing time > ⚠️ **Warning:** Browser Agent tasks can take significantly longer than other workflow actions due to real-time web interaction requirements. ### How to Review Browser Agent Results 1. **View the Output**: * The agent will return the requested information or confirmation of completed actions * Results appear in the standard output format for use in subsequent workflow steps 2. **Access Session Recording**: * After execution, two new buttons appear on the Browser Agent card: * **View Recording** - Opens a popup showing the step-by-step browser interactions * **Open Session** - Opens the browser session in a new window for review 3. **Analyze the Process**: * Use the recording to understand how the agent navigated the task * Review tab structure and interaction patterns * Identify any areas for task optimization ### Best Practices * **Start with simple tasks** to understand how the agent interprets instructions * **Be explicit about required information** to ensure accurate extraction * **Test tasks thoroughly** before deploying in production workflows * **Use clear, unambiguous language** in task descriptions * **Consider timeout implications** for time-sensitive workflows * **Review recordings** to optimize future task descriptions ### Troubleshooting * **If the agent gets stuck**: Review your task description for clarity and specificity * **For failed executions**: Check the session recording to identify where issues occurred * **For slow performance**: Consider breaking complex tasks into smaller, focused steps * **For unexpected results**: Refine your task instructions with more specific requirements ### Output Format The Browser Agent action outputs: * Extracted information or data as requested in the task * Confirmation of completed actions * Structured results ready for use in subsequent workflow steps * Access to session recordings for process review > πŸ’‘ **Tip:** Browser Agent results can be used as variables in other workflow actions, making it perfect for automated data collection, form filling, and web-based research tasks. # Human-in-the-loop ## Human-in-the-Loop Actions Human-in-the-loop actions allow you to pause automated workflows and request human input or approval before continuing. These actions ensure that critical decisions remain under human control while maintaining the efficiency of automation. ### Overview Human-in-the-loop functionality bridges the gap between full automation and human oversight. When a workflow reaches a human-in-the-loop action, it creates a task that appears in the assigned user's Request Inbox, sends notifications, and waits for their response before continuing. ### Key Benefits * **Quality Control**: Ensure critical decisions are reviewed by humans * **Flexibility**: Allow dynamic input that can't be predetermined * **Compliance**: Meet regulatory requirements for human approval * **Risk Management**: Prevent automated processes from making costly mistakes * **Contextual Decisions**: Leverage human judgment for complex scenarios ### Available Human-in-the-Loop Actions #### Request Decision Perfect for approval workflows, decision gates, and validation processes. Users receive a request with custom buttons and can approve, reject, or choose from multiple options. [Learn more about Request Decision β†’](/canvas-actions/human-in-the-loop/request-approval) #### Request Input Ideal for collecting additional information, form submissions, and data gathering. Users fill out customisable forms to provide the data needed for the workflow to continue. [Learn more about Request Input β†’](/canvas-actions/human-in-the-loop/request-input-page) ### How It Works **1. Workflow Execution** Your workflow runs automatically until it reaches a human-in-the-loop action. **2. Task Creation** The action creates a task in the Request Inbox with all relevant context and information. **3. User Notification** Assigned users receive email notifications and see the task in their Request Inbox. **4. Human Action** Users review the information and take the required action (approval, input, etc.). **5. Workflow Continuation** The workflow automatically continues based on the human response. ### Assignment Options All human-in-the-loop actions support flexible assignment: * **Specific User**: Assign to an individual team member * **Variable Assignment**: Use workflow variables to dynamically assign tasks * **Role-Based Assignment**: Assign to user roles (Owners, Builders, Operators) > πŸ’‘ **Best Practice**: Use role-based assignment for better scalability and coverage when team members are unavailable. ### Shared Request Options Both actions support extra context to help the assignee respond quickly and accurately: * **Priority**: Mark the request as Low, Medium, High, or Urgent so assignees know what to tackle first * **SLA deadline**: Set how long the request should take to resolve, so overdue requests stand out * **Attachments**: Include files from earlier workflow steps alongside the request * **Related record**: Link the request to a data table record so the assignee can see the record it concerns ### Managing Human-in-the-Loop Tasks All tasks created by human-in-the-loop actions are managed through the Request Inbox, which provides: * Centralised task management * Email notifications * Complete audit trail * Filtering and sorting capabilities * Real-time status updates Requests can also be **reassigned** to a different person from the Request Inbox, and completed requests can be **re-opened** if a decision needs revisiting. ### Routing Follow-ups to the Same Person Both actions output who resolved the request. You can use this to assign a later request in the same workflow to the same person, keeping a whole case with one handler. ### Design Considerations When implementing human-in-the-loop actions: **Provide Clear Context** * Include relevant information from previous workflow steps * Write clear titles and descriptions * Add any necessary background information **Set Appropriate Urgency** * Consider workflow timing when assigning tasks * Use descriptive titles to indicate priority * Establish team response time expectations **Plan for Edge Cases** * Consider what happens if tasks aren't completed promptly * Design alternative paths for different approval outcomes * Include escalation procedures for urgent requests > ⚠️ **Important**: Human-in-the-loop actions will pause your workflow until completed. Plan your process flow accordingly to avoid bottlenecks. # Request Approval The Request Decision action pauses your workflow to request human approval or decision-making. It creates customisable decision requests with multiple button options and routes the workflow based on the user's choice. ### Overview Request Decision is perfect for: * **Approval workflows**: Get sign-offs on documents, proposals, or requests * **Decision gates**: Route workflows based on human judgment * **Quality control**: Review content or processes before continuation * **Compliance verification**: Ensure regulatory requirements are met * **Multi-option decisions**: Provide several response choices ### How to Add Request Decision **How to add the Request Decision node** 1. Click the "Add Action" button in the top left corner of your canvas 2. Navigate to the "Operator Actions" section 3. Select "Request Decision" 4. The node will be added to your workflow canvas 5. Connect it between the appropriate workflow steps ### Configuring the Request Decision Node #### Title Configuration **How to set the decision title** 1. Click on the Request Decision node to open its configuration 2. In the "Title" field, enter a clear, descriptive title 3. Use specific language that tells the assignee exactly what they're deciding 4. Keep titles concise but informative **Examples of effective titles:** * "Approve Marketing Campaign Budget" * "Review Customer Refund Request" * "Authorise Employee Time Off" #### Description Configuration **How to write the decision description** 1. In the "Description" field, provide comprehensive context 2. Include relevant information from previous workflow steps 3. Explain what the decision will trigger 4. Add any deadlines or urgency indicators **Best practice for descriptions:** * Include key details and background information * Reference specific amounts, dates, or criteria * Explain the consequences of each option * Keep language clear and professional #### Button Configuration **How to set up decision buttons** 1. Each decision option gets its own button configuration 2. Click on a button to customise it 3. Set the button text (what the assignee will see) 4. Choose the button style from these options: * **Default**: Standard button appearance * **Success**: Green styling for positive actions (like "Approve") * **Secondary**: Neutral styling for alternative options * **Destructive**: Red styling for negative actions (like "Reject") * **Outline**: Border-only styling for less prominent options * **Ghost**: Minimal styling for subtle actions * **Link**: Text-only styling for informational actions **Button configuration tips:** * Use clear, action-oriented language ("Approve", "Reject", "Request Changes") * Limit to 2-4 buttons to avoid decision paralysis * Match button style to the action type (Success for approvals, Destructive for rejections) * Order buttons logically with the most common action first #### Priority and SLA Deadline **How to set urgency** 1. Choose a **Priority** (Low, Medium, High, or Urgent) so assignees can see at a glance what needs attention first 2. Optionally set an **SLA deadline** for how long the request should take to resolve, so overdue requests stand out in the Request Inbox #### Attachments and Related Record **How to give the assignee more context** 1. Add **Attachments** to include files from earlier workflow steps, for example the invoice or document being decided on 2. Link a **Related record** by pointing the request at a data table record, so the assignee can open the record the decision concerns #### Assignee Configuration **How to assign decision tasks** 1. In the "Assignees" section, choose your assignment method: **Assign to Specific User:** * Select individual team members from the dropdown * Best for dedicated approvers or specific role holders * Ensures the right person handles domain-specific decisions **Assign by Role:** * Choose from available roles (Owners, Builders, Operators) * Automatically includes all users with that role * Better for coverage when specific people might be unavailable * Scales automatically as team membership changes > πŸ’‘ **Assignment Strategy**: Use role-based assignment for broader coverage, specific user assignment for specialised decisions. Requests can also be reassigned later from the Request Inbox if the wrong person received one. ### Workflow Branching with Request Decision #### How Button Responses Create Workflow Paths **Setting up branching logic** 1. Each button you configure creates a separate output connection point 2. The button clicked by the assignee determines which workflow path is followed 3. Connect different subsequent actions to each button's output 4. Design different workflow paths for different outcomes **Example branching scenarios:** * **"Approve" button**: Continue to next automation step * **"Reject" button**: Send notification email and end workflow * **"Request Changes" button**: Loop back to earlier workflow step * **"Escalate" button**: Assign to different approver or management #### Accessing Decision Data **How to use the decision in subsequent steps** 1. The chosen button and any reason given are stored as workflow variables 2. Reference them in later actions using variable syntax 3. The **resolvedBy** output tells you who resolved the request. Use it to assign a follow-up request to the same person, so one handler sees a case through end to end 4. Use the decision to customise subsequent workflow behaviour ### Best Practices #### For Clear Decision Requests * **Be Specific**: Clearly state what is being decided * **Provide Context**: Include all information needed for an informed decision, using attachments and a related record where they help * **Set Expectations**: Use the priority and SLA deadline to indicate urgency * **Include Relevant Data**: Reference key details like amounts, dates, or metrics #### For Button Design * **Logical Organisation**: Order buttons from most to least likely * **Visual Hierarchy**: Use styles that match button importance * **Clear Language**: Use action verbs that indicate exactly what happens * **Appropriate Quantity**: Stick to essential options only #### For Assignment Strategy * **Consider Coverage**: Ensure someone will always be available to respond * **Match Expertise**: Assign to people with relevant knowledge or authority * **Plan for Absences**: Use role-based assignment or multiple assignees for critical decisions * **Document Process**: Make decision criteria and expectations clear ### Working with Decision Tasks #### What Happens When a Decision is Requested 1. **Workflow Pauses**: Execution stops at the Request Decision node 2. **Task Creation**: A task is created in the assignee's Request Inbox 3. **Notification Sent**: Email notification sent to all assigned users 4. **Awaiting Response**: Workflow remains paused until someone responds 5. **Decision Recorded**: Button choice is saved with timestamp and user info 6. **Workflow Continues**: Execution resumes following the chosen button path #### Decision Task Details Assignees will see: * The title and description you configured * All available button options with their styling * The priority and any SLA deadline * Any attachments and the related record, if provided * Information about the workflow that generated the request > πŸ’‘ If a decision needs revisiting, a completed request can be re-opened from the Request Inbox, which rewinds the flow to that step. > ⚠️ **Important**: Workflows will remain paused until someone completes the decision task. Plan for appropriate timeouts or escalation procedures. ### Troubleshooting **Common Issues and Solutions** **Assignees not receiving notifications** * Verify email settings in user profiles * Check that assigned users have proper permissions * Confirm users are active in the organisation **Workflow not continuing after a decision** * Ensure button outputs are connected to subsequent actions * Check that the next actions don't have configuration errors * Verify the workflow is published and active **Too many options causing confusion** * Simplify to the most essential decision points * Use clear, distinct button labels * Provide detailed descriptions for complex scenarios # Request Input Page ## Request Input The Request Input node pauses your workflow to collect information from users through customisable forms. When the workflow reaches this node, it creates a task in the assigned user's Request Inbox and waits for form completion before continuing. ### Overview Request Input is perfect for collecting: * Missing information that wasn't available at workflow start * User feedback and qualitative responses * File uploads and document attachments * Dynamic data based on previous workflow steps * Verification or confirmation of existing information ### How to Add Request Input **How to add the Request Input node** 1. Click "Add Action" in the top left corner or click a connection circle on an existing node 2. Navigate to the "Operator Actions" section 3. Select "Request Input" 4. The node appears on your canvas 5. Connect it to your workflow sequence ### Configuring Request Input #### Title **How to set the request title** 1. Click on the Request Input node to open configuration 2. Enter a clear, specific title in the "Title" field 3. Use action-oriented language that tells users exactly what to provide **Examples:** * "Provide Customer Feedback Details" * "Upload Project Documentation" * "Enter Budget Information" #### Description **How to write effective descriptions** 1. In the "Description" field, explain what information is needed and why 2. Include any formatting requirements or examples 3. Set clear expectations for response time 4. Reference relevant context from earlier workflow steps **Description best practices:** * Explain the purpose behind the request * Provide examples for complex fields * Include deadlines if time-sensitive * Clarify what happens after submission #### Form Fields **How to configure form fields** 1. Click "Add Field" to create new input fields 2. Configure each field's name, type, and requirements 3. Arrange fields in logical order 4. Set appropriate validation rules #### Available Field Types **Text** * Single-line text input * Best for names, short descriptions, simple data * Can set character limits **Number** * Numeric input with validation * Supports decimal values * Can set minimum and maximum ranges **Toggle** * Boolean on/off switch * Perfect for yes/no questions * Set default state (enabled/disabled) **Single Select** * Choose one option from a dropdown list * Create custom option lists * Good for categories and standardised responses **Multi Select** * Choose multiple options from a list * Users can select several relevant items * Useful for tags, features, or multiple categories **Date Picker** * Calendar-based date selection * Standardised date format * Can restrict date ranges **File Upload** * Accept documents, images, and other files * Set file type restrictions * Configure file sise limits **Item List** * Allow users to create dynamic lists * Users can add/remove multiple entries * Good for variable-length data collection **Lookup** * Reference existing data or external sources * Connect to knowledge bases * Validate against existing records > πŸ’‘ Request Input uses the same field configurations as forms elsewhere in Lleverage, so the field types will feel familiar. #### Field Configuration Options **How to configure individual fields** 1. **Field Name**: Internal reference for the data 2. **Field Label**: What users see on the form 3. **Required/Optional**: Whether the field must be completed 4. **Default Values**: Pre-populated data when applicable 5. **Validation Rules**: Constraints specific to the field type #### Field Suggestions Fields can carry **suggested values** drawn from earlier workflow steps. The person completing the form sees each suggestion and can accept it with a click or type their own answer instead. The value is never filled in silently, so a human always confirms it. > πŸ’‘ Suggestions speed up form completion while keeping the person in control, which matters for data you need a human to verify. #### Priority, SLA Deadline, Attachments, and Related Record **How to add urgency and context to the request** 1. Choose a **Priority** (Low, Medium, High, or Urgent) so assignees know what to tackle first 2. Optionally set an **SLA deadline** for how long the request should take to resolve, so overdue requests stand out in the Request Inbox 3. Add **Attachments** to show files from earlier workflow steps alongside the form, for example the document the answers relate to 4. Link a **Related record** by pointing the request at a data table record, so the assignee can see the record the request concerns #### Assignees **How to assign input tasks** **Assign to Specific User:** 1. Select individual team members from the dropdown 2. Best when specific expertise is required 3. Ensures the right person provides accurate information **Assign by Role:** 1. Choose from available roles: * **Owners**: Organisation or project owners * **Builders**: Users who can create workflows * **Operators**: Users who can run workflows 2. Automatically includes all users with that role 3. Better coverage when specific people might be unavailable > πŸ’‘ Consider who has the knowledge or access needed to complete the request accurately when choosing assignment method. Requests can also be reassigned later from the Request Inbox, and completed requests can be re-opened if something needs revisiting. ### How Request Input Works #### The Request Process 1. **Workflow Execution**: Your workflow runs until it reaches the Request Input node 2. **Task Creation**: A task is created in the assignee's Request Inbox 3. **Notification**: Assigned users receive email notifications 4. **Form Completion**: Users access and complete the input form 5. **Data Capture**: Submitted information is stored as workflow variables 6. **Workflow Continuation**: The workflow resumes with the new data available #### What Users See Assigned users receive: * Email notification with direct link to the task * Task in their Request Inbox with your title and description * Form with all configured fields * Clear indication of required vs optional fields * Submit button to complete the task ### Using Submitted Data **How to access input data in subsequent steps** 1. Use variable syntax: `{{request_input.field_name}}` 2. Reference in AI prompts, emails, or integrations 3. Apply conditional logic based on submitted values 4. Pass data to external systems **Available data includes:** * All form field responses * Submission timestamp * Any uploaded files * **resolvedBy**: who completed the form. Use this to assign a follow-up request in the same workflow to the same person, so one handler sees a case through end to end ### Form Design Best Practices #### For Better Completion Rates * Keep forms as short as possible * Only request essential information * Use clear, descriptive field labels * Provide examples for complex fields * Group related fields together #### For Data Quality * Choose appropriate field types for validation * Mark required fields clearly * Set reasonable default values where possible * Use consistent formatting across similar forms #### For User Experience * Order fields in logical sequence * Provide help text for ambiguous fields * Minimise the number of required fields * Test forms with actual users before deployment ### Common Use Cases **Customer Information Collection** * Gathering additional customer details mid-workflow * Collecting feedback or satisfaction ratings * Requesting clarification on support tickets **Document and File Collection** * Requesting supporting documentation * Collecting signed agreements or contracts * Gathering evidence or proof materials **Project and Task Management** * Collecting project requirements * Gathering status updates from team members * Requesting resource allocation information **Approval Support Information** * Collecting justification for approval requests * Gathering additional context for decision-making * Requesting budget or timeline details ### Troubleshooting **Users not receiving requests** * Check email settings in user profiles * Verify assigned users have proper permissions * Confirm users are active in the organisation **Forms not submitting** * Ensure all required fields are completed * Check for validation errors * Verify field configurations are correct **Data not available in next steps** * Check variable syntax in subsequent actions * Ensure field names match between form and usage * Verify workflow connections are proper **Low completion rates** * Simplify forms by removing non-essential fields * Improve field descriptions and instructions * Follow up on pending requests > ⚠️ Workflows remain paused at Request Input nodes until someone completes the form. Plan for appropriate follow-up procedures. # Extracting Information Extracting Information actions in Lleverage allow you to pull content from various sources and make it available for use in your workflow. These specialized actions help transform data from websites, documents, and images into usable text that can be processed by other actions. ## Extracting Information Actions in Lleverage Extracting Information actions in Lleverage allow you to pull content from various sources and make it available for use in your workflow. These specialized actions help transform data from websites, documents, and images into usable text that can be processed by other actions. ### Key Features * **Multiple source options** including websites, documents, and images * **Automatic text extraction** from various file formats * **Document conversion capabilities** for processing complex content * **OCR functionality** for images containing text * **Seamless integration** with other workflow actions ### How to Add Extracting Information Actions 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Select "Extracting Information" from the categories 3. Choose an extraction action, such as: * Scrape Website * Extract Text from Document * Convert Document to Images * Extract Text from Images 4. Click on your chosen action to add it to your canvas > πŸ’‘ All extraction actions share a similar card structure with a title, icon, variable output, and configuration area. ### How to Configure Extraction Actions #### How to Use Scrape Website 1. Provide a URL in the input field 2. Set the extraction depth: * **Single page**: Extracts content from only the specified URL * **Direct links**: Extracts content from the specified URL and pages directly linked from it * **Links of links**: Performs a deeper crawl, including pages linked from direct links > ⚠️ Be cautious when testing this action with larger websites, as it may not be as fast as expected for extensive crawling. Consider using an integration action for more complex website crawling if necessary.

Scrape Website Action

#### How to Use Extract Text from Document 1. Specify the file input in the configuration area 2. This can be a URL or a file input from a trigger action (using a variable) 3. Supports multiple file types including PDF, Word, Excel, and CSV > πŸ’‘ This action automatically extracts readable text content from the specified document.

Extract Text from Documents Action

#### How to Use Convert Document to Images 1. Specify the file input in the configuration area 2. This can be a URL or a file input from a trigger action (using a variable) 3. The action will convert document pages to image format > πŸ’‘ This is particularly useful when you need to process document content as images rather than text.

Convert Document to Images Action

#### How to Use Extract Text from Images 1. Provide an image URL or specify a file input variable 2. The action will use OCR technology to extract any text present in the image > πŸ’‘ This action is ideal for processing screenshots, photos of documents, or any images containing text.

Extract Text from Image Action

### File Tools Alongside extraction, this category includes actions for creating and reshaping files inside your workflow: * **Create PDF**: Generates a styled PDF document from HTML or Markdown content, ideal for producing reports, letters, or summaries at the end of a workflow * **Create Excel**: Builds an Excel workbook from structured data, with support for multiple sheets * **Merge PDF**: Combines multiple PDF files into a single PDF, in the order you provide them * **Split Excel by Sheet**: Splits a multi-sheet Excel workbook into separate files, one per sheet, which is useful before processing each sheet independently * **Chunk PDF**: Splits a PDF into smaller PDFs of a set number of pages, which helps when processing very large documents piece by piece * **Convert Spreadsheet to JSON**: Turns CSV or Excel files into structured data your workflow can work with directly * **Convert PDF Invoice to UBL**: Uses AI to read a PDF invoice and produce a UBL invoice, with the option to provide extra context to improve accuracy (available on paid plans) > πŸ’‘ File tool outputs are files themselves, so you can chain them: for example, create several PDFs and then merge them into one document to send. ### Important Considerations 1. All extraction actions require their respective input fields to be filled 2. Each extraction action has only one required configuration field 3. File uploads are handled through variables from trigger actions, not direct uploads 4. The extraction results can be referenced using the variable output of each action 5. These actions are specifically built by Lleverage for pulling information that can be used within workflows > ⚠️ For optimal performance, ensure you're using the appropriate extraction action for your specific content type. ### How Extraction Actions Work in Your Workflow 1. Add the appropriate extraction action based on your source material 2. Configure the action with the required input source 3. Connect the action to subsequent actions that will process the extracted information 4. When the workflow runs, the extraction action will pull content from the specified source 5. The extracted content becomes available as a variable for other actions to use > πŸ’‘ Extraction actions are often used early in a workflow to gather information for AI processing in subsequent steps. # Using Information Using Information actions in Lleverage help you access, store, and utilize data from various sources within your workflow. These actions enable you to query databases, add contextual information, and retrieve professional data from LinkedIn. ### Key Features * **Database connectivity** for accessing structured data * **Contextual input** for adding custom information to workflows * **LinkedIn data retrieval** for professional insights * **Simple configuration** for each specialized information source * **Text outputs** that integrate easily with other actions ### How to Add Using Information Actions 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Select "Using Information" from the categories (also found in "All" and "Tools") 3. Choose one of the five information actions: * Query Database * Knowledge Context * Get LinkedIn Profile * Get LinkedIn Company * Search LinkedIn for Companies 4. Click on your chosen action to add it to your canvas > πŸ’‘ For information about Knowledge Bases, please refer to the dedicated Knowledge Bases documentation. ### How to Configure Information Actions #### How to Use Query Database 1. Select a database connection from the dropdown menu * Choose from existing PostgreSQL or MySQL connections * Alternatively, change to an input and reference a connection variable 2. Use the code editor to write your SQL query 3. The action will execute this query against the selected database when the workflow runs > πŸ’‘ This action allows you to integrate database information directly into your workflow logic.

Query Database Action

#### How to Use Knowledge Context 1. Simply enter text in the provided text editor 2. This free-form text becomes available as context elsewhere in your workflow > πŸ’‘ This is particularly useful for adding fixed rules, guidelines, or context that needs to be programmatically accessible in your workflow.

Context Action

#### How to Use Get LinkedIn Profile 1. Configure the required fields: * First name (required) * Last name (optional) * Company name or domain (required) 2. The action will retrieve the LinkedIn profile information matching these details > ⚠️ Either company name or domain is required along with the first name to find the correct profile.

LinkedIn Profile Action

#### How to Use Get LinkedIn Company 1. Enter the company name in the required field 2. The action will retrieve information about the specified company from LinkedIn > πŸ’‘ This provides company details that can be used for business intelligence or personalization in your workflow.

Get Linkedin Company Action

#### How to Use Search LinkedIn for Companies 1. Enter the search query for company names 2. The action will return a list of companies matching your search criteria > πŸ’‘ All LinkedIn-related actions output text data that can be easily processed by subsequent actions in your workflow.

Search LinkedIn for Companies Action

### Important Considerations 1. Database queries require proper SQL syntax for the selected database type 2. Knowledge Context provides a simple way to add fixed information without external sources 3. LinkedIn actions require accurate input information to return useful results 4. All actions in this category output text data for further processing 5. These actions are designed to fetch and prepare information for use by AI and other processing actions > ⚠️ When using database queries, ensure your query is optimized to avoid performance issues in your workflow. ### How Information Actions Work in Your Workflow 1. Add the appropriate information action based on your data source needs 2. Configure the action with the required inputs 3. Connect the action to subsequent actions that will use the retrieved information 4. When the workflow runs, the information action will fetch or prepare the specified data 5. The information becomes available as a variable for other actions to process > πŸ’‘ These actions are typically used to gather specific information that enhances the capabilities of AI processing actions. # Custom Code Advanced Coding actions in Lleverage provide powerful capabilities for developers and technical users to integrate custom code and external services into their workflows. These actions allow for HTTP requests to external APIs and custom JavaScript code execution. ### Key Features * **External API integration** through HTTP requests * **Custom code execution** using JavaScript * **Flexible configuration options** for different request types * **Header customization** for authentication and data formatting * **Variable integration** for dynamic request parameters ### How to Add Advanced Coding Actions 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one node to create a connection 2. Find these actions in either: * The "All" tab * The "Tools" tab 3. Choose one of the two available actions: * Send HTTP Request * Run Code 4. Click on your chosen action to add it to your canvas > πŸ’‘ While these are advanced coding actions, they appear in the general tools section rather than a dedicated "Advanced Coding" category. ### How to Configure Advanced Coding Actions #### How to Use Send HTTP Request 1. Configure the required URL field with the endpoint you want to access 2. Select the HTTP method (required): * **GET**: Retrieve data from the server * **POST**: Send data to the server * **PUT**: Update existing resources * **DELETE**: Remove resources 3. Choose a Content-Type (required): * **application/json**: For sending JSON-formatted data * **multipart/form-data**: For sending files and form data * **text/plain**: For sending plain text * **application/x-www-form-urlencoded**: For sending form data as URL variables 4. Set up headers: * **Authorization**: For authentication tokens or credentials * **Additional Headers**: Click "Add Headers" to include custom headers * For each additional header, provide a name and value * Delete individual headers as needed > ⚠️ Follow the developer guidelines for any API you're connecting to, as requirements vary between services. Tools like Postman can help you understand how HTTP requests work.

HTTP Request Action

#### How to Use Run Code 1. The action provides a JavaScript code editor 2. Enter your custom JavaScript code in the editor 3. The code will execute when this action runs in your workflow 4. This action doesn't require any input, as you can pass through this action if needed > πŸ’‘ To use variables in your code, use the advanced variable syntax with double curly braces: `{{ variableName }}`

Run Code Action with an example input

### Important Considerations for HTTP Requests 1. Different APIs require different headers and authentication methods 2. Content-Type determines how your data will be formatted when sent 3. You can add multiple custom headers for specialized API requirements 4. Variables can be used in any field (URL, headers, etc.) for dynamic requests 5. Responses from HTTP requests can be referenced as variables in subsequent actions > ⚠️ Always test your HTTP requests thoroughly to ensure they're correctly formatted for your target API. ### Important Considerations for Run Code 1. Only JavaScript is supported in the Run Code action 2. Code executes within Lleverage's environment, not locally 3. Advanced variable syntax is required to access workflow variables 4. The code can process data and return results to the workflow 5. Complex operations may require careful error handling > πŸ’‘ The Run Code action is particularly useful for data transformation, calculations, and conditional logic that's difficult to achieve with standard actions. ### How Advanced Coding Actions Work in Your Workflow 1. Add the appropriate advanced coding action to your workflow 2. Configure the action with the necessary parameters or code 3. Connect the action to subsequent steps that will use its output 4. When the workflow runs, the action will execute its request or code 5. The results become available as variables for other actions to process > πŸ’‘ These advanced actions provide significant flexibility for extending your workflow capabilities beyond the standard actions. # Subworkflows Subworkflows in Lleverage allow you to use existing workflows within other workflows, creating modular, reusable components that enhance efficiency and organization. This powerful feature helps you avoid duplicating work and creates logical groupings of functionality. ### Key Features * **Workflow reusability** for common processes and tools * **Modular design** that simplifies complex automations * **Organizational structure** for grouping related functions * **Consistent execution** of standardized processes * **Easy maintenance** through centralized updates ### How to Add Subworkflows 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one node to create a connection 2. Find Subworkflows in either: * The "Subworkflows" tab * The "Subworkflows" subcategory in other tabs 3. Select from available published workflows in your project 4. Click on your chosen Subworkflow to add it to your canvas > πŸ’‘ You can only add Subworkflows that you have access to within your project.

Adding Subworkflow through the Add Modal

### Understanding Subworkflow Cards 1. Subworkflow cards have a distinct appearance: * They display as a "stat card" shape, different from standard action cards * They include the workflow name and description * They show a branch icon by default (if no custom icon was specified) 2. The card header contains: * Variable output in the top left corner * The same action controls as other action cards * Connection points on left and right sides 3. The card body shows: * A description (generated automatically if none was specified in the original workflow) * Configuration fields that match the trigger inputs of the referenced workflow > ⚠️ When selecting a Subworkflow card, you only select the top card portion, not the entire visual representation.

Subworkflow Card

### How to Configure Subworkflows 1. When you add a Subworkflow, the configuration area will match the trigger inputs of the original workflow 2. Fill in these fields just as you would for a standard trigger 3. You can rename the Subworkflow node in your canvas if desired 4. Connect the Subworkflow to other actions using the standard connection points > πŸ’‘ The configuration options for a Subworkflow are determined by what inputs were defined in the original workflow's trigger. ### How to Edit Subworkflows 1. To edit a Subworkflow from your main workflow: * Select the Subworkflow card on your canvas * Click the three-dot menu in the top right corner * Select "Edit" (pencil icon) from the options menu 2. This will navigate you to that workflow for editing: * The breadcrumbs at the top will show your location * You can make changes to the Subworkflow if you have access * To return to your main workflow, use the breadcrumbs navigation 3. Important publishing considerations: * Any changes you make to a Subworkflow must be published for them to take effect in your main workflow * Unpublished changes will be saved as drafts but won't affect the current published version * The publishing process follows the same workflow as other Lleverage components > ⚠️ Remember that changes to a Subworkflow may affect all workflows that use it, not just your current main workflow.

Subworkflow Breadcrumbs

### How Subworkflows Execute 1. When your main workflow runs and reaches a Subworkflow: * The main workflow pauses execution * The Subworkflow runs with the inputs you've provided * Once the Subworkflow completes, the main workflow resumes * The Subworkflow's output becomes available to subsequent actions 2. This execution pattern creates a nested structure: * Main workflow β†’ Subworkflow β†’ Main workflow continues > ⚠️ If a Subworkflow encounters an error, it may affect the execution of the main workflow depending on your error handling configuration. ### Important Subworkflow Considerations 1. **Access Controls**: * You can only add Subworkflows that you have access to in your project * You can see Subworkflows added by others in shared workflows, but cannot add them yourself unless you have access * You can only edit Subworkflows if you have edit access to them 2. **Workflow States**: * Only published workflows can be used as Subworkflows * Changes to the original workflow will affect all instances where it's used as a Subworkflow * Draft changes don't affect the published version used by other workflows 3. **Design Principles**: * Create Subworkflows for processes that are used repeatedly * Design Subworkflows to be modular and focused on specific tasks * Ensure Subworkflows have clear input requirements and outputs 4. **Visual Representation**: * The distinct card shape makes it easy to identify Subworkflows in your canvas * The branch icon is the default, but can be customized in the original workflow > πŸ’‘ Think of Subworkflows as functions or methods in programming - reusable components that perform specific tasks and can be called from multiple places. ### Benefits of Using Subworkflows 1. **Reduced Duplication**: Build a process once and use it in multiple workflows 2. **Easier Maintenance**: Update one Subworkflow to affect all instances where it's used 3. **Better Organization**: Group related actions into logical units 4. **Simplified Complexity**: Break down complex workflows into manageable components 5. **Standardization**: Ensure consistent execution of critical processes > πŸ’‘ Using Subworkflows effectively can significantly reduce the time needed to build complex automations while improving their reliability and maintainability. # External Apps Integration External apps let your workflows and agents work with the tools your organisation already uses: email, spreadsheets, document stores, CRMs, ERPs and more. Connect an account once, and every workflow and agent in the project can use it, within the limits you set. ### Two kinds of integrations Lleverage offers two kinds of integrations, which connect in different ways: * **Native Lleverage integrations** - built and maintained by Lleverage for the core business systems our customers rely on. These connect through Lleverage's own connection dialog in Settings > Connections, where you also control exactly what each connection is allowed to do. * **Pipedream-powered apps** - thousands of additional apps available through our partner Pipedream. These connect through a popup flow: when you connect one, a popup explains that Lleverage uses Pipedream to link your account, and you sign in from there. > πŸ’‘ Some apps are available in both forms. Gmail, for example, exists as a native Lleverage integration and as a Pipedream-powered app. ### Native integrations The native integrations cover these apps: * **Email and communication** - Gmail, Microsoft Outlook, Microsoft Outlook Calendar, Google Calendar, Slack, Microsoft Teams * **Files and documents** - Microsoft SharePoint, Microsoft OneDrive, Microsoft Excel, Google Drive, Google Docs, Google Sheets, Notion * **Customer service and forms** - Zendesk, Typeform * **CRM** - Zoho CRM * **ERP** - Microsoft Dynamics 365 Business Central, Microsoft Dynamics 365 Finance & Operations, Dynamics NAV, SAP S/4HANA * **Data and analytics** - Google BigQuery > πŸ’‘ **Reliability advantage**: native integrations are built, tested and maintained by the Lleverage team, so they are the best choice for business-critical workflows. ### Where connections live Connections are managed from **Settings > Connections** in your project. The page shows the apps you can connect, the accounts that are already connected, and lets you open any connection to manage what it can do. ### How to connect a native integration 1. **Open Settings > Connections** in your project. 2. **Pick the app** you want to connect from the list. 3. **Choose what the connection should be able to do.** You can enable all of the app's actions or just a subset. Lleverage only requests the permissions the selected actions need, and you can fine-tune the list later from the connection's settings. 4. **Choose who should have access.** A shared connection is available to everyone in the project and can be used on workflow nodes; a personal connection is private to you. 5. **Choose how to connect.** Pick "Connect Now" to sign in with an account you have access to, or "Send Authentication Link" to ask someone else to connect on your behalf. 6. **Sign in and grant access.** For most apps this is the familiar sign-in screen of the provider (Google, Microsoft, Slack and so on). > πŸ’‘ Only asking for the permissions your selected actions need keeps the sign-in prompt small and makes approvals easier for IT teams. ### Sending an authentication link to a colleague If the account that should be connected belongs to someone else, for example a shared mailbox owned by an administrator, you don't need their password: 1. In the connect dialog, choose **Send Authentication Link**. 2. Enter the recipient's email address (and optionally their name). 3. The recipient receives an email with a secure link. When they open it and sign in, the connection is created in your project. > ⚠️ Authentication links expire after 48 hours. If the link isn't used in time, simply send a new one. ### Microsoft service-to-service access Microsoft Outlook and Microsoft Outlook Calendar can also connect without any individual signing in, using an app registration your IT team creates in Microsoft Azure. This suits shared mailboxes and fully automated processes. 1. In the connect dialog, choose **App Registration (S2S)**. 2. Enter the **Client ID**, **Client Secret** and **Tenant ID** from your organisation's Azure app registration. The dialog includes a step-by-step setup guide for creating one. 3. Choose **Connect Now**, or use **Send Link Instead** to email a secure form to your IT administrator so they can enter the details themselves. ### When Microsoft admin approval is needed Some Microsoft organisations require an administrator to approve new apps before anyone can connect. If that applies to yours, the connect flow pauses and explains that administrator consent is required. You can copy an approval link to send to your Microsoft administrator; once they approve it, everyone in your organisation can connect. There is also a **Generate an approval link** option in the connect dialog if you want to request approval up front. ### Other sign-in methods Most native integrations sign in with the provider's own account login (OAuth). A few work differently: * **Zendesk** asks for your Zendesk subdomain (the first part of your Zendesk web address) before you sign in. * **SAP S/4HANA** supports signing in with a username and password or an API key for on-premise systems, alongside cloud sign-in. * **Dynamics NAV** connects with a username and password. * **ERP connections** (Business Central, Finance & Operations, Dynamics NAV, SAP S/4HANA) are set up together with the Lleverage team, because they need configuration specific to your environment. Contact support or your account manager to get started. ### Controlling what a connection may do Every connection has its own action policy: the list of actions it allows, and which of those need a person's approval before they run. This is the main safety control for what an agent may do with a connection. * **Read only** - allow read actions only. * **Read & write** (recommended) - allow all actions, but changes ask for approval before running. * **Full access** - allow all actions without approval. Beyond the presets, you can enable or disable individual actions and switch **Ask for approval** on or off per action. An action with approval switched on pauses until someone confirms it, so you can let an agent draft and prepare work while keeping a person in charge of anything that changes data or sends messages. > πŸ’‘ Start with Read & write. Agents can then do useful work straight away, while every change still passes through a person. ### Triggers and actions Integrations provide two things to build with: * **Actions** do something in the connected app: send an email, add a row, create a ticket. * **Triggers** start a workflow when something happens in the connected app: a new email arrives, a form is submitted, a sales order is created. Some triggers check the app for changes on a schedule (polling), so there can be a short delay before the workflow starts. Others react instantly because the app notifies Lleverage the moment something happens (webhooks). Either way, setup is the same: pick the trigger, choose a connection, and configure what to listen for. ### How to add an external app to a workflow 1. Click the "Add Action" button in your workflow 2. Navigate to the External Apps section by either: * Scrolling to the bottom of the "All" tab, or * Selecting the "External Apps" tab directly 3. Browse through providers (native integrations appear first, followed by Pipedream-powered apps) 4. Click on a provider to see all available actions for that service 5. Select the specific action you want to add to your workflow > πŸ’‘ External apps are organised differently from other nodes: they're grouped by provider first because of the large number of integrations available.
### How to connect a Pipedream-powered app 1. Select the external app node in your workflow 2. Click "Add New Connection" in the configuration panel 3. A popup explains that Lleverage uses Pipedream to connect your account 4. Click "Continue", then sign in to the app and grant access 5. Configure the specific action settings 6. Check "Optional Properties" at the bottom for additional advanced settings > ⚠️ Be mindful of your plan limits when using external apps. Frequent calls to integrations might consume your workflow runs quickly, especially with scheduled triggers.
### How to use external apps as triggers 1. Add an integration trigger to your workflow 2. Select your provider and choose a connection 3. Choose the specific trigger event (e.g. "When email received," "When form submitted") 4. Set up any additional trigger conditions 5. Configure how the workflow should respond to the trigger > ⚠️ When using external apps as triggers, be especially careful with automation frequency as triggers may run automatically and consume your plan's workflow runs. ### How to request missing integrations If you can't find a specific integration or action you need, you have two options: #### Option 1: Connect directly via API 1. Navigate to the Advanced category section in the action picker 2. Select "Send HTTP Request" 3. Follow the provider's development documentation to configure: 1. URL endpoint 2. Authentication headers 3. Request method (GET, POST, PUT, DELETE) 4. Request body and parameters 4. Test the connection using the Run panel > πŸ’‘ This method gives you immediate access to any API without waiting for official integration support. #### Option 2: Request an integration from the team 1. **From the connect dialog in Settings > Connections**: use the "Request a connection" link to tell us which tool you'd like to connect 2. **In the Add Action menu**: search for the action and click "Request Action" when no results appear 3. **Through support**: contact the support team via the chat feature > πŸ’‘ Native integrations are prioritised for core business systems and high-volume enterprise use cases. ### Best practices * **Test the connection**: run a simple action after connecting to confirm everything works * **Use variables**: pass data between integrations using Lleverage variables * **Handle errors**: add error handling for external calls that might fail * **Keep policies tight**: enable only the actions a connection actually needs, and use approvals for anything that changes data * **Choose native when available**: use native integrations for mission-critical workflows requiring maximum reliability # Gmail Gmail integration in Lleverage enables you to automate email workflows directly within your automations. Connect your Gmail or Google Workspace account to send emails, manage labels, find messages, and handle attachments seamlessly. > πŸ’‘ Gmail is available both as a **native Lleverage integration** (connected through Lleverage's own connection dialog in Settings > Connections) and as a **Pipedream-powered app** (connected through the popup flow). The native integration covers sending, replying, drafts, labels, threads, search and attachments, plus triggers for new emails received and sent. ### Key Features * **Email management** - Send, draft, archive, and find emails programmatically * **Label operations** - Add, remove, and list Gmail labels for organisation * **Attachment handling** - Download attachments from emails to use in workflows * **Triggers** - Start workflows when a new email is received or sent (native integration) ### How to Add Gmail Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Gmail integration: * Select "External Apps" from the categories * Search for "Gmail" in the provider list, or * Scroll down to find Gmail in the alphabetical list 3. Click on Gmail to view available actions 4. Select your desired Gmail action from the list of available options > πŸ’‘ **Tip**: When searching for integrations, search by provider name (Gmail) rather than specific action names for best results. ### How to Connect Your Gmail Account **Native integration** 1. Go to **Settings > Connections** in your project 2. Pick Gmail from the list of apps 3. Choose which actions the connection should allow and who should have access (shared or personal) 4. Choose "Connect Now" and sign in with Google, or send an authentication link so a colleague can connect on your behalf **Pipedream-powered app** 1. Click "Connect Gmail Account" in any Gmail action 2. Choose to connect a new account or use an existing connection 3. A popup will appear stating "Lleverage uses Pipedream to connect your account" 4. Click "Continue" to accept terms and conditions 5. Select "Sign in with Google" 6. Choose which Google account to connect 7. Grant necessary permissions for data access 8. Click "Continue" once successfully connected > ⚠️ **Important**: Gmail data may not auto-update immediately. Refresh the page if newly created labels or emails don't appear in dropdowns. ### How to Configure Gmail Actions #### How to Send Emails 1. Connect your Gmail or Google Workspace account 2. Configure the required fields: * **To**: Select recipients from dropdown or input manually/via variable * **Subject**: Enter email subject line * **Email Body**: Compose your message content 3. Optional properties (expand for advanced configuration): * **CC**: Add carbon copy recipients * **BCC**: Add blind carbon copy recipients * **From Name**: Customize sender display name * **From Email**: Specify sending email address * **Reply To**: Set different reply-to address * **Body Type**: Choose HTML or plain text format * **Attachment File Names**: Attach files by name * **Attachment URLs**: Include files via URL * **In Reply To**: Reference previous message * **MIME Type**: Set message format > πŸ’‘ **Use case**: Automate follow-up emails, send reports on schedule, or trigger email notifications based on workflow conditions. #### How to Manage Email Labels **Add Label to Email** 1. Connect your Gmail account 2. Select the target message from dropdown or input variable 3. Choose the label to apply from available options **Remove Label from Emails** 1. Connect your Gmail account 2. Select the message containing the label 3. Choose which label to remove from dropdown **List Labels** 1. Connect your Gmail account 2. This action automatically retrieves all existing labels in your account > πŸ’‘ **Use case**: Organize emails automatically based on content, sender, or workflow triggers. Create automated filing systems for different types of correspondence. #### How to Find Emails 1. Connect your Gmail account 2. Configure search parameters: * **Search Query**: Use Gmail search syntax to find specific emails * **Include Spam and Trash**: Check box to include these folders * **Max Results**: Set maximum number of emails to return 3. The action uses Google's search engine to locate matching emails > πŸ’‘ **Use case**: Retrieve emails for processing, find attachments to download, or locate specific correspondence for workflow decisions. #### How to Handle Attachments **Download Attachment** 1. Connect your Gmail account 2. Select the message containing the attachment 3. Choose which attachment to download 4. Optional: Specify a custom filename > πŸ’‘ **Use case**: Process invoices, extract data from documents, or save important files from incoming emails for further workflow steps. #### How to Create Email Drafts 1. Connect your Google Workspace account 2. Configure draft content: * **To**: Specify recipients * **Subject**: Set email subject * **Email Body**: Compose draft content 3. Optional properties (same as Send Email): * CC, BCC, attachments, reply settings, and formatting options > πŸ’‘ **Use case**: Prepare emails for manual review before sending, create templates for team members, or stage emails based on workflow conditions. #### How to Archive Emails 1. Connect your Gmail account 2. Select the message to archive from dropdown or variable input 3. The email will be moved to the archived folder > πŸ’‘ **Use case**: Automatically archive processed emails, clean up inbox after workflow completion, or organize emails based on workflow outcomes. ### Important Considerations * All input fields support custom text, dropdown selections, and workflow variables * Gmail integration requires appropriate permissions for the actions you want to perform * Dropdown options populate based on your connected account's current data * Some actions may require Google Workspace rather than personal Gmail accounts * Label and message dropdowns will show "No options" if no data is available > ⚠️ **Security Note**: Only grant the minimum permissions necessary for your workflow requirements. With the native integration, Lleverage only requests the permissions the actions you selected actually need. ### How Gmail Actions Work in Your Workflow 1. Add the appropriate Gmail action based on your email automation needs 2. Connect your Gmail or Google Workspace account securely 3. Configure the action with required fields and optional properties 4. Connect the action to other workflow steps as needed 5. When the workflow runs, the Gmail action will execute the specified email operation 6. Results and data from Gmail actions become available as variables for subsequent actions > πŸ’‘ **Best Practice**: Use Gmail actions to close the loop on your workflows - notify stakeholders, send results, or trigger human actions based on automated processing. # Outlook Microsoft Outlook integration in Lleverage enables you to automate email and contact management workflows directly with your Microsoft 365 or Outlook account. Manage emails, organize contacts, handle attachments, and streamline communication processes seamlessly. ### Key Features * **Email management** - Send, reply, draft, and organize emails programmatically * **Contact operations** - Create, update, and search contacts in your address book * **Label and folder management** - Organize emails with labels and move between folders * **Attachment handling** - Download email attachments for workflow processing * **Email search** - Find specific emails and contacts using search criteria * **Workflow approvals** - Suspend workflows pending email-based approvals * **Secure connection** - Direct integration with Microsoft accounts ### How to Add Outlook Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Outlook integration: * Select "External Apps" from the categories * Search for "Outlook" or "Microsoft" in the provider list, or * Scroll down to find Outlook in the alphabetical list 3. Click on Outlook to view available actions 4. Select your desired Outlook action from the available options ### How to Connect Your Microsoft Account **Initial Setup** 1. Go to **Settings > Connections** in your project 2. Pick Microsoft Outlook from the list of apps 3. Choose which actions the connection should allow and who should have access (shared or personal) 4. Choose "Connect Now" and sign in with Microsoft, or send an authentication link so a colleague can connect on your behalf 5. Your account will be available for selection in Outlook actions **Connecting without an individual account** Outlook also supports service-to-service access using an app registration your IT team creates in Microsoft Azure. Choose "App Registration (S2S)" in the connect dialog and enter the Client ID, Client Secret and Tenant ID, or send a secure link to your IT administrator so they can enter the details themselves. > πŸ’‘ If your Microsoft organisation requires administrator approval for new apps, the connect flow pauses and gives you an approval link to share with your Microsoft administrator. Once approved, everyone in your organisation can connect. > ⚠️ **Important**: Some dropdowns may show "No options" if your account doesn't contain relevant data (contacts, folders, etc.). ### How to Configure Outlook Actions #### How to Manage Contacts **Update Contact** 1. Connect your Microsoft account 2. Select the contact to update from the dropdown (if available) 3. Configure optional properties: * **Given Name**: First name of the contact * **Surname**: Last name of the contact * **Email Address**: Contact's email address (dropdown or manual input) * **Recipients**: Additional recipient information > πŸ’‘ **Use case**: Automatically update contact information when details change, synchronize contact data from forms, or maintain current contact records based on workflow inputs. **Create Contact** 1. Connect your Microsoft account 2. The contact will be added to your root contacts folder 3. Configure optional properties: * **Given Name**: Contact's first name * **Surname**: Contact's last name * **Email Address**: Contact's email address * **Recipients**: Additional contact details > πŸ’‘ **Use case**: Automatically add new leads to your contact list, create contacts from form submissions, or build your address book from workflow data. **List Contacts** 1. Connect your Microsoft account 2. Configure optional properties: * **Email Address**: Filter contacts by email * **Max Results**: Limit the number of contacts returned > πŸ’‘ **Use case**: Retrieve contact lists for mail merges, export contact data, or find specific contacts for further processing. **Find Contacts** 1. Connect your Microsoft account 2. Enter a **Search String** to locate specific contacts 3. Optional properties: * **Max Results**: Limit search results > πŸ’‘ **Use case**: Locate specific contacts for personalized communications, find contact details for workflow decisions, or search for contacts meeting specific criteria. #### How to Manage Emails **Send Email** 1. Connect your Microsoft account 2. Configure optional properties: * **Recipients**: Select from dropdown or input manually * **CC Recipients**: Add carbon copy recipients * **BCC Recipients**: Add blind carbon copy recipients * **Subject**: Email subject line * **Content Type**: Choose email format (HTML/plain text) * **Content**: Email body content * **File Path**: Attach files to the email > πŸ’‘ **Use case**: Send automated notifications, distribute reports on schedule, or trigger email communications based on workflow conditions. **Reply to Email** 1. Connect your Microsoft account 2. Select the **Message ID** of the email you're replying to 3. Configure optional properties: * **Recipients**: Additional recipients for the reply * **CC Recipients**: Carbon copy recipients * **BCC Recipients**: Blind carbon copy recipients * **Subject**: Reply subject (usually auto-generated) * **Content**: Your reply message * **File Path**: Attach files to the reply > πŸ’‘ **Use case**: Automate responses to specific types of emails, send acknowledgments for received messages, or provide automated customer service replies. **Create Draft Email** 1. Connect your Microsoft account 2. Configure optional properties (same as Send Email): * Recipients, CC, BCC, subject, content type, content, and file attachments 3. The email will be saved as a draft rather than sent immediately > πŸ’‘ **Use case**: Prepare emails for manual review before sending, create templates for team use, or stage emails based on workflow conditions. #### How to Organize Emails **Move Email to Folder** 1. Connect your Microsoft account 2. Specify the **Message ID** of the email to move 3. Select the **Folder ID** where the email should be moved > πŸ’‘ **Use case**: Automatically file emails based on content or sender, organize processed emails, or implement automated email sorting rules. **Add Label to Email** 1. Connect your Microsoft account 2. Specify the **Message ID** of the target email 3. Enter the **Label** to apply to the email > πŸ’‘ **Use case**: Tag emails for easy identification, categorize messages by type or priority, or mark emails as processed by workflows. **Remove Label from Email** 1. Connect your Microsoft account 2. Select the **Message ID** of the email 3. Specify the **Label** to remove > πŸ’‘ **Use case**: Clean up email organization, remove temporary tags after processing, or update email categorization. #### How to Search and List Items **Find Email** 1. Connect your Microsoft account 2. Configure search parameters: * **Filter**: Specify search criteria for finding emails * **Max Results**: Limit the number of results returned > πŸ’‘ **Use case**: Locate specific emails for processing, find attachments to download, or retrieve correspondence for workflow decisions. **List Labels** 1. Connect your Microsoft account 2. This action retrieves all available labels/categories in your account > πŸ’‘ **Use case**: Get available labels for email organization, synchronize label systems, or provide options for email categorization. **List Folders** 1. Connect your Microsoft account 2. Configure optional properties: * **Max Results**: Limit the number of folders returned > πŸ’‘ **Use case**: Display available folders for email organization, synchronize folder structures, or provide folder options for email filing. #### How to Handle Attachments **Download Attachment** 1. Connect your Microsoft account 2. Specify the **Message ID** containing the attachment 3. Enter the **Attachment ID** to download 4. Optionally specify a **File Name** for the downloaded attachment > πŸ’‘ **Use case**: Process invoices or documents from emails, extract data from attached files, or save important attachments for further workflow processing. #### How to Set Up Email Approvals **Approve Workflow** 1. Connect your Microsoft account 2. Configure approval settings: * **Recipients**: Who should receive the approval request * **Subject**: Subject line for the approval email 3. The workflow will pause until approval is received > πŸ’‘ **Use case**: Require manager approval for expenses, get sign-off on content before publishing, or ensure human oversight for sensitive automated actions. ### Important Considerations * All input fields support custom text, dropdown selections, and workflow variables * Dropdown options populate based on your connected account's current data * Some dropdowns may show "No options" if your account doesn't contain relevant data * Message IDs, Folder IDs, and Attachment IDs are typically obtained from other Outlook actions * Integration requires appropriate Microsoft 365 or Outlook account permissions > ⚠️ **Security Note**: Only grant the minimum permissions necessary for your workflow requirements when connecting your Microsoft account. ### How Outlook Actions Work in Your Workflow 1. Add the appropriate Outlook action based on your email or contact automation needs 2. Connect your Microsoft account securely 3. Configure the action with required fields and optional properties 4. Connect the action to other workflow steps as needed 5. When the workflow runs, the Outlook action will execute the specified operation 6. Results and data from Outlook actions become available as variables for subsequent actions > πŸ’‘ **Best Practice**: Use Outlook actions to integrate email communication seamlessly into your business processes - from lead management to automated reporting and approval workflows. # Microsoft Outlook Calendar Microsoft Outlook Calendar integration in Lleverage connects your workflows and agents to your calendar, so they can schedule and manage events, keep other systems in sync, and react automatically when the calendar changes. ### How to Connect 1. **Go to Settings > Connections** in your project 2. **Pick Microsoft Outlook Calendar** from the list of apps 3. **Choose which actions** the connection should allow and who should have access (shared or personal) 4. **Choose "Connect Now"** and sign in with Microsoft, or send an authentication link so a colleague can connect on your behalf **Connecting without an individual account** Outlook Calendar also supports service-to-service access using an app registration your IT team creates in Microsoft Azure. Choose "App Registration (S2S)" in the connect dialog and enter the Client ID, Client Secret and Tenant ID, or send a secure link to your IT administrator so they can enter the details themselves. > πŸ’‘ If your Microsoft organisation requires administrator approval for new apps, the connect flow gives you an approval link to share with your Microsoft administrator. ### What Outlook Calendar Can Do * **Events** - create, update and delete events, and retrieve a single event's details * **Browsing** - list events over a period and list the calendars in the account * **Responding** - accept, decline or tentatively accept an event invitation ### Triggers Outlook Calendar provides three triggers, so workflows can start automatically when: * **An event is created** * **An event is updated** * **An event is cancelled** Microsoft notifies Lleverage when these events happen, so workflows start straight away. > πŸ’‘ **Use case**: Prepare a briefing document before every external meeting, sync calendar changes to a project tracker, or notify the team when a key meeting is cancelled. ### Important Considerations * The connection works with the calendars the signed-in account can access * With service-to-service access, actions can work with any user's calendar in your organisation, so keep the connection's action policy tight # Slack Slack integration in Lleverage enables you to automate team communication and collaboration workflows directly within your Slack workspace. Send messages, manage channels, upload files, and interact with users seamlessly to keep your team connected and informed. ### Key Features * **Message management** - Send, reply, and update messages across channels and users * **Channel operations** - Set topics, descriptions, and manage channel members * **File sharing** - Upload files directly to Slack channels with comments * **User management** - Update profiles, set status, and manage user groups * **Advanced messaging** - Use Block Kit, markdown formatting, and scheduled messages * **Search and retrieval** - Find messages, list users, and retrieve conversation threads * **Secure connection** - Slack is a native Lleverage integration, connected through Lleverage's own connection dialog ### How to Add Slack Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Slack integration: * Select "External Apps" from the categories * Find "Slack" in the top 10 popular integrations, or * Scroll down to find Slack in the alphabetical list 3. Click on Slack to view available actions 4. Select your desired Slack action from the comprehensive list > πŸ’‘ **Tip**: Slack appears in the top 10 integrations due to its popularity and extensive automation capabilities. ### How to Connect Your Slack Account **Initial Setup** 1. Go to **Settings > Connections** in your project 2. Pick Slack from the list of apps 3. Choose which actions the connection should allow and who should have access (shared or personal) 4. Choose "Connect Now" and sign in to your Slack workspace, or send an authentication link so a colleague can connect on your behalf 5. Your connected account will be available across all Slack actions > ⚠️ **Important**: When data is available (channels, users, etc.), dropdown options will populate automatically. Otherwise, you can input values manually or use workflow variables. ### How to Configure Optional Properties **Understanding Optional Properties** 1. Click on "Optional Properties" to see available configuration options 2. Select the properties you want to add - they'll appear as input fields above 3. Configure each property based on its type: * **Toggle**: On/off switches for boolean options * **Input**: Text fields for custom values * **Dropdown**: Selection from available options 4. To remove optional properties, click them again in the Optional Properties menu > πŸ’‘ **This pattern applies to all Slack actions** - use optional properties to customize behavior without cluttering the basic interface. ### How to Send Messages #### How to Send Basic Messages **Send Message to Public or Private Channel** 1. Connect your Slack account 2. Select the target **Channel** from dropdown or input manually 3. Enter your **Text** message content 4. Configure optional properties: * **Send Text as Slack Markdown**: Enable rich formatting * **Schedule Message**: Set delivery time * **Customize Bot Settings**: Modify bot appearance * **Reply to Thread**: Respond to specific message * **Add Message Metadata**: Include additional data * **Configure Unfurl Settings**: Control link previews > πŸ’‘ **Use case**: Send automated notifications, share updates across teams, or broadcast announcements based on workflow triggers. **Send Message to User Group** 1. Connect your Slack account 2. Enter **Text** message content 3. Configure optional properties: * **Users**: Specify target user group * **Channel**: Select communication channel * Plus all standard messaging options (markdown, scheduling, etc.) > πŸ’‘ **Use case**: Alert specific teams about issues, send targeted updates to project groups, or notify stakeholders about workflow completion. #### How to Send Advanced Messages **Send Message Advanced** 1. Connect your Slack account 2. Select **Channel** or input destination 3. Enter **Text** content 4. Additional optional properties include: * **Attachments**: Add file attachments * **Parse**: Control message parsing behavior * **Link Names**: Enable automatic username/channel linking * **Add Blocks**: Reference existing blocks or configure manually > πŸ’‘ **Use case**: Create rich, formatted messages with attachments, interactive elements, or complex layouts for comprehensive team communication. **Send Large Message (3000+ Characters)** 1. Connect your Slack account 2. Select target **Channel** 3. Enter **Text** content (supports over 3000 characters) 4. Same optional properties as standard messaging > πŸ’‘ **Use case**: Share detailed reports, comprehensive updates, or lengthy documentation directly in Slack without character limitations. **Build and Send Block Kit Message** 1. Connect your Slack account 2. Select target **Channel** 3. Configure optional properties: * **Notification Text**: Fallback text for notifications * **Add Blocks**: Reference existing blocks or configure manually (maximum 5 blocks) * Plus standard messaging options > πŸ’‘ **Use case**: Create interactive messages with buttons, forms, or rich layouts for user engagement, surveys, or actionable notifications. #### How to Reply to Messages **Reply to Message Thread** 1. Connect your Slack account 2. Select the **Channel** containing the original message 3. Enter **Text** for your reply 4. Specify **Message Timestamp** of the original message 5. Optional properties include: * **Send Channel Message**: Make reply visible to entire channel * Plus standard formatting and scheduling options > πŸ’‘ **Use case**: Provide automated responses to support requests, follow up on specific conversations, or add context to ongoing discussions. ### How to Manage Channels and Users #### How to Configure Channels **Set Channel Topic** 1. Connect your Slack account 2. Select the target **Channel** 3. Enter the new **Topic** text > πŸ’‘ **Use case**: Update channel topics based on project phases, current sprint information, or dynamic status updates from workflows. **Set Channel Description** 1. Connect your Slack account 2. Select the target **Channel** 3. Enter the new **Purpose** (description) text > πŸ’‘ **Use case**: Maintain current channel descriptions, update project information, or reflect changing team responsibilities. #### How to Manage Users and Groups **Update Profile** 1. Connect your Slack account 2. Configure optional properties to update: * **Display Name**: Public display name * **First Name**: User's first name * **Last Name**: User's last name * **Phone**: Contact phone number * **Pronouns**: User's pronouns * **Title**: Job title or role * **Email**: Contact email address * **User**: Target user to update > πŸ’‘ **Use case**: Automatically update team member information, sync HR data with Slack profiles, or maintain current contact details. **Set Status** 1. Connect your Slack account 2. Enter **Status Text** for the status message 3. Configure optional properties: * **Status Emoji**: Add emoji to status * **Status Expiration**: Set when status expires > πŸ’‘ **Use case**: Automatically set "in meeting" status during scheduled calls, update availability based on calendar events, or reflect workflow states. **Update Group Members** 1. Connect your Slack account 2. Select the **User Group** to modify 3. Configure optional properties: * **Users to Add**: Add new members to the group * **Users to Remove**: Remove existing members * **Team**: Specify team context > πŸ’‘ **Use case**: Dynamically manage project teams, update access groups based on role changes, or maintain current team membership. ### How to Search and Retrieve Information #### How to Find Content **Find Message** 1. Connect your Slack account 2. Enter **Query** to search for specific messages 3. Configure optional properties: * **Team**: Specify team context * **Max Results**: Limit number of results * **Sort**: Choose sorting method * **Sort Direction**: Ascending or descending order > πŸ’‘ **Use case**: Locate specific conversations for follow-up, find important information shared in channels, or retrieve historical context for decisions. #### How to List Information **List Users** 1. Connect your Slack account 2. Retrieves all users in the workspace 3. Optional properties: * **Team**: Filter by team * **Page Size**: Control results per page * **Number of Pages**: Limit total pages retrieved > πŸ’‘ **Use case**: Generate team directories, create user lists for notifications, or audit workspace membership. **List Members in Channel** 1. Connect your Slack account 2. Select the target **Channel** 3. Optional properties: * **Return Usernames**: Include username data * **Page Size** and **Number of Pages**: Control result pagination > πŸ’‘ **Use case**: Audit channel membership, create targeted communication lists, or monitor team participation. **List Group Members** 1. Connect your Slack account 2. Select the **User Group** to examine 3. Optional properties for pagination control > πŸ’‘ **Use case**: Verify group membership, generate contact lists, or audit access permissions. **List Replies** 1. Connect your Slack account 2. Select the **Channel** containing the thread 3. Specify **Message Timestamp** of the parent message 4. Optional properties for pagination > πŸ’‘ **Use case**: Retrieve conversation threads for analysis, follow discussion outcomes, or archive important conversations. ### How to Share Files #### How to Upload Files **Upload File** 1. Connect your Slack account 2. Select the target **Channel** 3. Specify **File Path** of the file to upload 4. Optional properties: * **Initial Comment**: Add description or context to the file > πŸ’‘ **Use case**: Automatically share generated reports, upload processed documents, or distribute files created by workflows to relevant team channels. ### How to Update Messages #### How to Modify Existing Messages **Update Message** 1. Connect your Slack account 2. Select the **Channel** containing the message 3. Specify **Message Timestamp** of the message to update 4. Enter new **Text** content 5. Configure **Send as User** toggle (on for user, off for bot) 6. Optional properties: * **Attachments**: Modify attached content > πŸ’‘ **Use case**: Update status messages with current information, correct automated messages, or modify shared content based on workflow changes. ### Important Considerations * All input fields support manual text entry, dropdown selections, and workflow variables * Dropdown options populate automatically when workspace data is available * Message timestamps are required for thread replies and message updates * Bot vs. user messaging affects how messages appear in Slack * Optional properties provide extensive customization without interface complexity * File uploads require valid file paths from your workflow > ⚠️ **Permission Note**: Ensure your Slack bot has appropriate permissions for the channels and actions you want to automate. ### How Slack Actions Work in Your Workflow 1. Add the appropriate Slack action based on your communication needs 2. Connect your Slack account securely through Settings > Connections 3. Configure required fields and desired optional properties 4. Connect the action to other workflow steps as needed 5. When the workflow runs, the Slack action will execute the specified communication 6. Results from Slack actions become available as variables for subsequent workflow steps > πŸ’‘ **Best Practice**: Use Slack actions to keep teams informed throughout your automated processes - from status updates to final results and required actions. # Microsoft Teams Microsoft Teams integration in Lleverage lets your workflows react to what happens in your Teams channels. Connect a Teams account and start workflows automatically whenever a new message is posted in a channel you choose. ### Key Features * **New channel message trigger** - Start a workflow the moment a message is posted in a specific team channel * **Instant reaction** - Teams notifies Lleverage when a message arrives, so workflows start straight away rather than waiting for a scheduled check * **Message details** - The trigger provides the message content and sender details for use in the rest of your workflow * **Secure connection** - Teams is a native Lleverage integration, connected with your Microsoft account > πŸ’‘ The Teams integration currently provides a trigger rather than actions: it starts workflows when something happens in Teams. To send messages or manage channels as workflow steps, combine it with other integrations such as Outlook or Slack, or request the Teams actions you need via support. ### How to Use the New Channel Message Trigger 1. **Add the trigger** to your workflow and choose Microsoft Teams 2. **Choose a connection**, or connect a Microsoft account if you haven't yet 3. **Select the team** you want to listen to 4. **Select the channel** within that team 5. **Save and publish** - the workflow now starts every time a new message is posted in that channel > πŸ’‘ **Use case**: Triage support requests posted in a shared channel, log important announcements, or kick off follow-up processes whenever a team posts an update. ### Important Considerations * The connected account needs access to the team and channel you want to listen to * Each trigger listens to one specific channel; add more triggers for more channels * Message content becomes available as variables for the rest of the workflow > ⚠️ **Frequency**: Busy channels can start the workflow often. Keep an eye on your plan's workflow runs when listening to high-traffic channels. # Google Calendar Google Calendar integration in Lleverage enables you to automate calendar management and scheduling workflows directly with your Google Calendar account. Create, update, and manage events, check availability, and coordinate schedules seamlessly within your automated processes. ### Key Features * **Event management** - Create, update, delete, and retrieve calendar events * **Calendar operations** - List calendars and retrieve calendar details * **Availability checking** - Get free/busy status for scheduling coordination * **Attendee management** - Add attendees to events and manage invitations * **Quick event creation** - Use natural language to create events rapidly * **Flexible scheduling** - Support for recurring events, time zones, and detailed configurations * **Secure connection** - Direct integration with Google Calendar API ### How to Add Google Calendar Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Google Calendar integration: * Select "External Apps" from the categories * Search for "Google Calendar" in the provider list, or * Scroll down to find Google Calendar in the alphabetical list 3. Click on Google Calendar to view available actions 4. Select your desired Calendar action from the comprehensive list ### How to Connect Your Google Calendar Account **Initial Setup** 1. Click "Connect Google Calendar Account" in any Calendar action 2. Follow the Google authentication process 3. Grant necessary calendar permissions 4. Your connected account will be available across all Calendar actions > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for reading, writing, and managing calendar events based on your workflow needs. ### How to Configure Google Calendar Actions #### How to Create Events **Create Event** 1. Connect your Google Calendar account 2. Choose **Type of Add** from the dropdown: * **Detailed Event**: Full event configuration with all options * **Quick Event**: Use natural language description 3. Configure optional properties: * **Calendar ID**: Specify which calendar to use (defaults to primary) * Plus additional properties based on event type selected > πŸ’‘ **Use case**: Automatically schedule appointments from form submissions, create recurring team meetings, or set up project milestones based on workflow triggers. **Add Quick Event** 1. Connect your Google Calendar account 2. Enter **Describe Event** using natural language (e.g., "Team meeting tomorrow at 2 PM") 3. Configure optional properties: * **Calendar ID**: Choose specific calendar * **Attendees**: Add participants to the event > πŸ’‘ **Use case**: Rapidly create events from conversational inputs, schedule meetings from chat commands, or add events using simple text descriptions without complex formatting. #### How to Manage Existing Events **Update Event** 1. Connect your Google Calendar account 2. Specify the **Event ID** of the event to modify 3. Configure optional properties to update: * **Calendar ID**: Move event to different calendar * **Event Title**: Change event name * **Event Start Date**: Modify start time * **Event End Date**: Adjust end time * **Event Location**: Update meeting location * **Event Description**: Change event details * **Attendees**: Modify participant list * **Repeat Frequency**: Adjust recurring pattern * **Time Zone**: Change time zone settings * **Send Updates**: Control notification settings > πŸ’‘ **Use case**: Update meeting details when project scope changes, modify recurring events based on schedule adjustments, or automatically reschedule events based on external factors. **Delete Event** 1. Connect your Google Calendar account 2. Specify the **Event ID** of the event to remove 3. Configure optional properties: * **Calendar ID**: Specify which calendar contains the event > πŸ’‘ **Use case**: Remove canceled meetings, clean up outdated events, or delete events when workflows determine they're no longer needed. #### How to Add Participants **Add Attendees to Event** 1. Connect your Google Calendar account 2. Specify the **Event ID** of the target event 3. Enter **Attendees** (email addresses of participants to add) 4. Configure optional properties: * **Calendar ID**: Specify calendar if needed * **Send Updates**: Control whether attendees receive notifications > πŸ’‘ **Use case**: Dynamically add team members to meetings based on project assignments, include stakeholders when certain conditions are met, or expand meeting participation based on workflow decisions. ### How to Retrieve Information #### How to Get Event Details **Retrieve Event Details** 1. Connect your Google Calendar account 2. Specify the **Event ID** to retrieve 3. Configure optional properties: * **Calendar ID**: Specify which calendar contains the event > πŸ’‘ **Use case**: Get current event information for workflow decisions, retrieve meeting details for processing, or extract event data for reporting purposes. **List Events** 1. Connect your Google Calendar account 2. Configure optional properties to filter results: * **Calendar ID**: Choose specific calendar * **ICS UID**: Filter by external calendar identifier * **Max Attendees**: Limit attendee information returned * **Max Results**: Control number of events retrieved * **Order By**: Sort events (start time, creation date, updated date) * **Private Extended Properties**: Include custom properties * **Query**: Search for specific events * **Shared Extended Properties**: Include shared metadata * **Show Deleted**: Include deleted events * **Show Hidden Invitations**: Include declined invitations * **Single Events**: Expand recurring events * **Time Zone**: Specify time zone for results * **Time Minimum/Maximum**: Set date range filters * **Event Types**: Filter by event type > πŸ’‘ **Use case**: Generate reports on upcoming meetings, find events matching specific criteria, or retrieve schedules for resource planning and conflict detection. #### How to Check Availability **Retrieve Free/Busy Calendar Details** 1. Connect your Google Calendar account 2. **Calendar ID** is preset to "primary" but can be changed via dropdown 3. Set **Min Time** and **Max Time** for the availability window 4. Configure optional properties: * **Time Zone**: Specify time zone for the query > πŸ’‘ **Use case**: Check availability before scheduling meetings, coordinate schedules across team members, or determine optimal meeting times based on participant availability. #### How to Manage Calendars **List Calendars** 1. Connect your Google Calendar account 2. This action retrieves all calendars associated with your account > πŸ’‘ **Use case**: Provide calendar options for event creation, audit available calendars, or synchronize calendar lists with other systems. **Retrieve Calendar Details** 1. Connect your Google Calendar account 2. Configure optional properties: * **Calendar ID**: Specify which calendar to examine > πŸ’‘ **Use case**: Get calendar metadata, verify calendar permissions, or retrieve calendar settings for workflow configuration. ### Understanding Optional Properties **Flexible Configuration** * Optional properties allow extensive customization without cluttering the basic interface * You can add as many optional properties as needed for your specific use case * Each property provides additional control over event creation, updates, and retrieval * Properties vary by action but commonly include calendar ID, attendees, and notification settings > πŸ’‘ **Tip**: Start with basic configuration and add optional properties as your automation requirements become more sophisticated. ### Important Considerations * Event IDs are required for updating, deleting, or retrieving specific events * Calendar ID defaults to "primary" but can be specified for multi-calendar setups * Time zones are crucial for accurate scheduling across different locations * Attendee management affects invitation and notification behavior * Free/busy queries help prevent scheduling conflicts * Natural language event creation provides flexibility but may require refinement > ⚠️ **Best Practice**: Always specify time zones explicitly when working with events that involve participants in different locations. ### How Google Calendar Actions Work in Your Workflow 1. Add the appropriate Calendar action based on your scheduling needs 2. Connect your Google Calendar account securely 3. Configure required fields (event details, dates, participants, etc.) 4. Set optional properties for advanced functionality 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the Calendar action will execute the specified operation 7. Event data and calendar information become available as variables for subsequent actions ### Common Workflow Patterns **Automated Meeting Scheduling** * Create events automatically from form submissions or external triggers * Check availability before scheduling to prevent conflicts * Add attendees dynamically based on project assignments or roles **Event Management and Updates** * Update meeting details when project requirements change * Automatically reschedule recurring events based on external factors * Send notifications and manage attendee lists based on workflow conditions **Schedule Coordination** * Retrieve free/busy information to find optimal meeting times * List events for resource planning and conflict detection * Coordinate schedules across multiple calendars and team members > πŸ’‘ **Best Practice**: Use Google Calendar actions to seamlessly integrate scheduling into your business processes - from automated appointment booking to complex resource coordination and meeting management. # Sharepoint Microsoft SharePoint integration in Lleverage enables you to automate document management and list operations directly with your SharePoint Online environment. Create and manage lists, update items, and handle file operations seamlessly within your automated workflows. ### Key Features * **List management** - Create, retrieve, browse and delete SharePoint lists * **Item operations** - Create, update, retrieve, search and delete items within SharePoint lists * **File and folder handling** - Upload and download files, browse document libraries, and create folders * **Site integration** - Browse sites and tenants and work across multiple SharePoint sites * **Triggers** - Start workflows when a list item is created or updated * **Flexible input** - Support for dropdown selections and manual input with variables * **Secure connection** - SharePoint is a native Lleverage integration, connected through Lleverage's own connection dialog ### How to Add SharePoint Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to SharePoint integration: * Select "External Apps" from the categories * Search for "SharePoint" in the provider list, or * Scroll down to find SharePoint in the alphabetical list 3. Click on SharePoint to view available actions 4. Select your desired SharePoint action from the list ### What SharePoint Can Do The SharePoint integration provides a broad set of actions, grouped here by area: * **Sites and tenants** - Browse the SharePoint sites and tenants your account can access * **Lists** - Create, retrieve, browse and delete lists * **List items** - Create, update, retrieve, search and delete items in a list * **Files and folders** - Upload and download files, browse files in document libraries, and create folders It also provides two triggers, so workflows can start automatically when a **list item is created** or a **list item is updated**. ### How to Connect Your SharePoint Account **Initial Setup** 1. Go to **Settings > Connections** in your project 2. Pick Microsoft SharePoint from the list of apps 3. Choose which actions the connection should allow and who should have access (shared or personal) 4. Choose "Connect Now" and sign in with Microsoft, or send an authentication link so a colleague can connect on your behalf 5. Your connected account will be available across all SharePoint actions > πŸ’‘ **Permissions**: Ensure your account has appropriate permissions for the SharePoint sites and operations you want to automate. If your Microsoft organisation requires administrator approval for new apps, the connect flow gives you an approval link to share with your Microsoft administrator. ### How to Configure SharePoint Actions #### How to Manage Lists **Create List** 1. Connect your Microsoft SharePoint Online account 2. Select the target **Site** from dropdown or input manually 3. Enter the **Name** for your new list 4. Configure optional properties: * **Description**: Add a description explaining the list's purpose > πŸ’‘ **Use case**: Automatically create project-specific lists, set up tracking lists for workflows, or establish new data collection structures based on business requirements. #### How to Manage List Items **Create Item** 1. Connect your Microsoft SharePoint Online account 2. Select the target **Site** from dropdown 3. Choose the **List** where you want to create the item 4. Select the **Column** and configure the item data > πŸ’‘ **Use case**: Add new entries to tracking lists, create records from form submissions, or populate SharePoint lists with data processed by workflows. **Update Item** 1. Connect your Microsoft SharePoint Online account 2. Select the target **Site** from dropdown 3. Choose the **List** containing the item to update 4. Select the specific **Item** to modify 5. Configure the updated values for the item > πŸ’‘ **Use case**: Update project status in SharePoint lists, modify records based on workflow processing, or synchronize external data changes with SharePoint items. #### How to Handle Files **Download File** 1. Connect your Microsoft SharePoint Online account 2. Select the target **Site** from dropdown 3. Choose the **Drive ID** (document library) from dropdown 4. Select the **File ID** of the specific file to download 5. Optionally specify a **File Name** for the downloaded file > πŸ’‘ **Use case**: Retrieve documents for processing in workflows, download files for analysis or conversion, or extract SharePoint documents for use in other systems. ### Understanding Input Flexibility **Dropdown vs Manual Input** * Every dropdown field also accepts manual text input * You can use workflow variables in any field * Dropdown options populate based on your SharePoint account access * Manual input allows for dynamic values from previous workflow steps **Site Selection** * Choose from available SharePoint sites in your organization * Input site URLs manually if not appearing in dropdown * Use variables to dynamically select sites based on workflow conditions **List and Item Selection** * Lists populate based on the selected site * Items appear based on the chosen list * Drive IDs represent document libraries within the site > πŸ’‘ **Flexibility**: The combination of dropdown convenience and manual input flexibility makes SharePoint actions adaptable to various automation scenarios. ### Important Considerations * Site, list, and item dropdowns populate based on your SharePoint permissions * Drive IDs correspond to document libraries within SharePoint sites * File operations require appropriate file access permissions * Column selection depends on the list structure in your SharePoint environment * All input fields support both static values and dynamic workflow variables > ⚠️ **Permissions**: Ensure your SharePoint account has the necessary permissions for sites, lists, and documents you want to access through workflows. ### How SharePoint Actions Work in Your Workflow 1. Add the appropriate SharePoint action based on your document or list management needs 2. Connect your Microsoft SharePoint Online account securely 3. Configure required fields (site, list, item, file details, etc.) 4. Set optional properties for additional functionality 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the SharePoint action will execute the specified operation 7. Results and data become available as variables for subsequent workflow actions ### Common Workflow Patterns **Document Management** * Download files from SharePoint for processing in workflows * Combine with other actions to analyze or convert SharePoint documents * Use file data in subsequent workflow steps **List Automation** * Create lists automatically for new projects or processes * Update list items based on external system changes * Populate SharePoint lists with data from forms or other sources **Data Synchronization** * Keep SharePoint lists current with external data sources * Update items when workflow conditions are met * Create new items automatically from various triggers **Project Management** * Create project-specific lists and populate them with initial data * Update project status and tracking information automatically * Download project documents for processing or distribution > πŸ’‘ **Best Practice**: Use SharePoint actions to bridge your automated workflows with your organization's document management and collaboration systems, ensuring data consistency and accessibility across platforms. # Microsoft Excel Microsoft Excel integration in Lleverage connects your workflows and agents to Excel workbooks stored in your Microsoft 365 account, so they can read and write spreadsheet data, maintain tables, and keep workbooks up to date automatically. ### How to Connect 1. **Go to Settings > Connections** in your project 2. **Pick Microsoft Excel** from the list of apps 3. **Choose which actions** the connection should allow and who should have access (shared or personal) 4. **Choose "Connect Now"** and sign in with Microsoft, or send an authentication link so a colleague can connect on your behalf > πŸ’‘ If your Microsoft organisation requires administrator approval for new apps, the connect flow gives you an approval link to share with your Microsoft administrator. ### What Microsoft Excel Can Do * **Workbooks and worksheets** - create workbooks, and create, rename, delete and list worksheets * **Ranges** - read and write cell ranges, and find values within a range * **Tables** - list and read tables, add, update and delete table rows, and find values within a table > πŸ’‘ **Use case**: Append processed results to a shared workbook, look up reference data held in a table, or keep a report worksheet refreshed automatically. ### Important Considerations * The connection works with workbooks the signed-in account can access in Microsoft 365 * Table actions are the most reliable way to add and update rows, because the table keeps the structure consistent * Ranges use the familiar cell notation (e.g. A1:D10) # Microsoft OneDrive Microsoft OneDrive integration in Lleverage connects your workflows and agents to your OneDrive files, so they can store, retrieve and organise documents as part of your automated processes. ### How to Connect 1. **Go to Settings > Connections** in your project 2. **Pick Microsoft OneDrive** from the list of apps 3. **Choose which actions** the connection should allow and who should have access (shared or personal) 4. **Choose "Connect Now"** and sign in with Microsoft, or send an authentication link so a colleague can connect on your behalf > πŸ’‘ If your Microsoft organisation requires administrator approval for new apps, the connect flow gives you an approval link to share with your Microsoft administrator. ### What Microsoft OneDrive Can Do * **Files** - upload and download files, retrieve file details, and list or search the files in your drive * **Organising** - copy, move, rename and delete files and folders, and create new folders * **Sharing** - create sharing links for files and look up your drive's details > πŸ’‘ **Use case**: Save generated documents to a known folder, fetch files for processing in a workflow, or share results with a link the rest of the team can open. ### Important Considerations * The connection works with the signed-in account's OneDrive; shared files appear where that account can access them * Files downloaded in a workflow become available to later steps, such as data extraction or email attachments # Google Drive Google Drive integration in Lleverage enables you to automate file management, sharing, and collaboration workflows directly with your Google Drive account. Upload, organize, search, and manage files and folders seamlessly within your automated processes. ### Key Features * **File management** - Upload, update, move, and delete files and folders * **Search capabilities** - Find files, folders, forms, and spreadsheets using various criteria * **Shared drive operations** - Manage shared drives and access permissions * **Access control** - Handle access proposals and sharing permissions * **Organization tools** - Get folder IDs, manage file structure, and handle trash operations * **Content processing** - OCR support and indexable text handling * **Secure connection** - Direct integration with Google Drive API ### How to Add Google Drive Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Google Drive integration: * Select "External Apps" from the categories * Search for "Google Drive" in the provider list, or * Scroll down to find Google Drive in the alphabetical list 3. Click on Google Drive to view available actions 4. Select your desired Drive action from the comprehensive list ### How to Connect Your Google Drive Account **Initial Setup** 1. Click "Connect Google Drive Account" in any Drive action 2. Follow the Google authentication process 3. Grant necessary Drive permissions for file access and management 4. Your connected account will be available across all Drive actions > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for the level of file access and management your workflows require. ### How to Configure Google Drive Actions #### How to Manage Files **Upload File** 1. Connect your Google Drive account 2. Configure the file upload parameters based on your needs 3. Specify destination folder and file properties > πŸ’‘ **Use case**: Automatically save workflow outputs to Drive, upload processed documents, or store generated reports in organized folder structures. **Update File** 1. Connect your Google Drive account 2. Select **Update Type** from dropdown options: * **Upload content from file URL**: Update file content from a web URL * **Upload content from file path**: Update using local file path * **Update file metadata**: Modify file properties without changing content 3. Configure optional properties: * **File Name**: Change the file name * **MIME Type**: Specify file format * **Add Parents**: Move file to additional folders * **Remove Parents**: Remove file from folders * **Keep Revision Forever**: Preserve file history * **OCR Language**: Set language for optical character recognition * **Use Content as Indexable Text**: Enable text search within file > πŸ’‘ **Use case**: Update documents with new content, modify file metadata based on workflow processing, or reorganize files by changing parent folders. **Move File** 1. Connect your Google Drive account 2. Select the **File** to move 3. Configure optional properties: * **Drive**: Specify target shared drive * **Folder**: Choose destination folder > πŸ’‘ **Use case**: Organize files based on workflow outcomes, move completed documents to archive folders, or relocate files based on processing status. **Delete File** 1. Connect your Google Drive account 2. Select the **File** to delete permanently > πŸ’‘ **Use case**: Clean up temporary files, remove outdated documents, or delete files when workflows determine they're no longer needed. **Move File to Trash** 1. Connect your Google Drive account 2. Select the **File or Folder** to move to trash 3. Configure optional properties: * **Drive**: Specify which drive contains the file > πŸ’‘ **Use case**: Safely remove files while preserving recovery options, clean up workspace while maintaining file history, or handle file deletion with rollback capability. #### How to Search and Find Content **Search for Shared Drives** 1. Connect your Google Drive account 2. Enter **Search Query** to find specific shared drives 3. Configure optional properties: * **Use Domain Admin Access**: Access all organization drives (admin only) > πŸ’‘ **Use case**: Locate shared drives for automated file operations, audit organizational drive structure, or find drives for cross-team collaboration. **List Files** 1. Connect your Google Drive account 2. Configure optional properties to filter results: * **Drive**: Specify which drive to search * **Parent Folder**: Limit search to specific folder * **Fields**: Choose which file metadata to retrieve * **Filter Text**: Search using Google Drive query syntax * **Trashed**: Include or exclude deleted files > πŸ’‘ **Use case**: Generate file inventories, find files matching specific criteria, or retrieve file lists for processing or reporting. **Find Spreadsheets** 1. Connect your Google Drive account 2. Locate Google Sheets files in your drive > πŸ’‘ **Use case**: Identify data sources for workflow processing, locate spreadsheets for automated updates, or find sheets for data extraction. **Find Forms** 1. Connect your Google Drive account 2. Locate Google Forms in your drive > πŸ’‘ **Use case**: Connect forms to workflows for response processing, identify survey tools for data collection, or manage form-based automation triggers. **Find Folders** 1. Connect your Google Drive account 2. Locate folders for organization and file management > πŸ’‘ **Use case**: Identify folder structure for automated file organization, locate destination folders for file operations, or audit folder hierarchy. **Find Files** 1. Connect your Google Drive account 2. Search for files across your Google Drive using various criteria > πŸ’‘ **Use case**: Locate specific documents for processing, find files matching workflow conditions, or retrieve file lists for automated operations. #### How to Manage Shared Drives **Update Shared Drive** 1. Connect your Google Drive account 2. Select the **Drive** to update 3. Configure optional properties: * **Use Domain Admin Access**: Administrative access (if applicable) * **Background Image**: Set drive background * **Link Color**: Customize drive appearance * **Restrictions**: Set access and sharing limitations > πŸ’‘ **Use case**: Maintain shared drive settings, update branding and appearance, or modify access restrictions based on organizational changes. **Get Shared Drive** 1. Connect your Google Drive account 2. Configure optional properties: * **Shared Drive**: Specify which drive to examine * **Use Domain Admin Access**: Administrative access for all drives > πŸ’‘ **Use case**: Retrieve drive metadata for workflow decisions, audit shared drive settings, or get drive information for reporting purposes. **Create Drive** 1. Connect your Google Drive account 2. Create a new shared drive for team collaboration 3. Configure drive settings and permissions > πŸ’‘ **Use case**: Automatically set up shared drives for new projects, create collaborative spaces for teams, or establish organized drive structures for different departments. **Delete Shared Drive** 1. Connect your Google Drive account 2. Select the shared drive to permanently remove 3. Ensure all necessary files are backed up before deletion > πŸ’‘ **Use case**: Clean up unused shared drives, remove drives for completed projects, or manage organizational drive structure by removing obsolete collaborative spaces. #### How to Handle Access and Permissions **Resolve Access Proposals** 1. Connect your Google Drive account 2. Select the **File or Folder** with pending access requests 3. Choose **Access Proposal ID** to address 4. Select **Action** to take on the proposal 5. Configure optional properties: * **Drive Roles**: Set permission levels * **Send Notifications**: Control notification settings > πŸ’‘ **Use case**: Automate approval workflows for file access, manage permission requests systematically, or handle access control based on predefined criteria. **List Access Proposals** 1. Connect your Google Drive account 2. Configure optional properties: * **File or Folder**: Specify target for proposal list * **Drive**: Choose which drive to examine * **Max Results**: Limit number of proposals returned > πŸ’‘ **Use case**: Monitor pending access requests, audit permission workflows, or generate reports on sharing activity. #### How to Get File and Folder Information **Get File ID** 1. Connect your Google Drive account 2. Select the **File** to examine 3. Configure optional properties: * **Drive**: Specify which drive contains the file * **Fields**: Choose which metadata to retrieve > πŸ’‘ **Use case**: Retrieve file identifiers for other workflow actions, get file metadata for processing, or extract file information for integration with other systems. **Get Folder ID for Path** 1. Connect your Google Drive account 2. Enter the **Path** to the target folder 3. Configure optional properties: * **Drive**: Specify which drive to search > πŸ’‘ **Use case**: Convert folder paths to IDs for API operations, locate folders using path notation, or resolve folder references for automated file operations. ### Understanding Optional Properties **Flexible Configuration** * Optional properties vary by action but commonly include drive selection, field specification, and access controls * Configuration types include: * **Inputs**: Text fields for custom values * **Dropdowns**: Selection from available options * **Checkboxes**: Boolean settings for features * **Switches**: Toggle controls for functionality **Drive Selection** * Many actions support both personal Google Drive and shared drives * Use the drive parameter to specify which drive to operate on * Admin access options available for organizational management > πŸ’‘ **Tip**: Start with basic configuration and add optional properties as your automation requirements become more sophisticated. ### Important Considerations * File IDs are required for most file-specific operations * Shared drive access may require additional permissions * OCR and indexing features help with content searchability * Access proposals enable collaborative permission management * Trash operations provide safer file deletion with recovery options * Path-based operations help navigate complex folder structures > ⚠️ **Security**: Be cautious with delete operations and ensure proper permissions are set before automating file management tasks. ### How Google Drive Actions Work in Your Workflow 1. Add the appropriate Drive action based on your file management needs 2. Connect your Google Drive account securely 3. Configure required fields (files, folders, search criteria, etc.) 4. Set optional properties for advanced functionality 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the Drive action will execute the specified operation 7. File data and metadata become available as variables for subsequent workflow actions ### Common Workflow Patterns **Automated File Organization** * Upload workflow outputs to organized folder structures * Move files based on processing results or content analysis * Create folder hierarchies automatically for projects or processes **Document Processing** * Search for files matching specific criteria * Update file content or metadata based on workflow processing * Extract information from files for use in subsequent workflow steps **Collaboration Management** * Handle access proposals automatically based on predefined rules * Manage shared drive settings and permissions * Monitor and audit file sharing activity > πŸ’‘ **Best Practice**: Use Google Drive actions to seamlessly integrate file management into your business processes - from automated document processing to organized file storage and collaborative access control. # Google Docs Google Docs integration in Lleverage connects your workflows and agents to your documents, so they can create and edit docs, pull content out for processing, and export finished documents automatically. ### How to Connect 1. **Go to Settings > Connections** in your project 2. **Pick Google Docs** from the list of apps 3. **Choose which actions** the connection should allow and who should have access (shared or personal) 4. **Choose "Connect Now"** and sign in with Google, or send an authentication link so a colleague can connect on your behalf ### What Google Docs Can Do * **Creating and finding** - create new documents and find existing ones * **Reading** - retrieve a document's details and its full content * **Editing** - append content, insert text at a position, and replace text throughout a document * **Exporting** - export a document to other formats for sharing or storage > πŸ’‘ **Use case**: Generate a report from workflow data, fill in a template by replacing placeholder text, or pull a document's content into an AI step for summarising. ### Important Considerations * The connection works with documents the signed-in Google account can access * Replace text is handy for template-style documents: keep placeholders in the doc and let the workflow fill them in # Google Sheets Google Sheets integration in Lleverage enables you to automate spreadsheet operations and data management workflows directly with your Google Sheets account. Create, update, and manage spreadsheets, worksheets, rows, and cells while maintaining comprehensive data processing and analysis capabilities seamlessly within your automated processes. ### Key Features * **Spreadsheet management** - Create new spreadsheets and manage existing ones * **Worksheet operations** - Create, copy, delete, and list worksheets within spreadsheets * **Row manipulation** - Add, update, delete, and find rows with flexible data handling * **Cell operations** - Update individual cells and clear content * **Data retrieval** - Extract data from ranges, specific cells, or entire worksheets * **Batch operations** - Handle multiple rows and ranges efficiently * **Header support** - Work with spreadsheets that have header rows * **Drive integration** - Organize sheets within Google Drive folders ### Key Google Sheets Concepts **Understanding Google Sheets Structure** * **Spreadsheet**: Main container file that holds all worksheets and data * **Worksheet (Sheet)**: Individual tab within a spreadsheet containing cells arranged in rows and columns * **Cell**: Individual data container identified by column letter and row number (e.g., A1, B2, C10) * **Row**: Horizontal line of cells across the worksheet * **Column**: Vertical line of cells down the worksheet * **Range**: Group of cells defined using A1 notation (e.g., A1:C10 means cells from A1 to C10) * **Header Row**: First row of a worksheet containing column titles or field names * **A1 Notation**: Standard way to reference cells and ranges (A1 = first cell, B1:D5 = range from B1 to D5) **Data Management Concepts** * **Upsert**: Update existing data or insert new data if it doesn't exist * **Key Column**: Column used to identify unique records for updating or finding data * **Row Values**: Complete set of data for one row across multiple columns * **Cell Value**: Individual piece of data within a specific cell * **Start Index**: Beginning position for operations (row or column number) * **End Index**: Ending position for range operations **Google Drive Integration** * **Drive Folder**: Google Drive location where spreadsheets are stored * **Spreadsheet ID**: Unique identifier for each Google Sheets file * **Worksheet ID**: Unique identifier for each sheet tab within a spreadsheet * **My Drive**: Default Google Drive location (appears as first option in dropdown) ### How to Add Google Sheets Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Google Sheets integration: * Select "External Apps" from the categories * Search for "Google Sheets" in the provider list, or * Scroll down to find Google Sheets in the alphabetical list 3. Click on Google Sheets to view available actions 4. Select your desired Sheets action from the comprehensive list ### How to Connect Your Google Sheets Account **Initial Setup** 1. Click "Connect Google Sheets Account" in any Sheets action 2. Follow the Google authentication process 3. Grant necessary permissions for spreadsheet access and management 4. Your connected account will be available across all Sheets actions > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for creating, reading, and modifying spreadsheets your workflows need to access. ### How to Configure Google Sheets Actions #### How to Create and Manage Spreadsheets **Create Spreadsheet** 1. Connect your Google Sheets account 2. Enter **Title** for the new spreadsheet 3. Configure optional properties: * **Drive**: Choose Google Drive folder location * **Folder**: Specify subfolder for organization > πŸ’‘ **Use case**: Automatically create new spreadsheets for monthly reports, generate project-specific data sheets, or establish new workbooks from workflow triggers. **Get Spreadsheet by ID** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** from dropdown 3. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Use case**: Retrieve spreadsheet metadata for workflow decisions, verify spreadsheet existence before operations, or get spreadsheet information for reporting. #### How to Manage Worksheets **Create Worksheet** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** from dropdown 3. Enter **Title** for the new worksheet 4. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Use case**: Add new sheets for different data categories, create monthly tabs in yearly reports, or establish worksheet structure based on workflow requirements. **List Worksheets** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** from dropdown 3. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Use case**: Audit spreadsheet structure, retrieve available worksheets for data operations, or get worksheet lists for dynamic processing. **Copy Worksheet** 1. Connect your Google Sheets account 2. Select source **Spreadsheet ID** from dropdown 3. Choose **Worksheet ID** to copy 4. Select destination **Spreadsheet ID** from dropdown 5. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Use case**: Duplicate worksheet templates, copy data structures to new projects, or replicate successful worksheet formats across multiple spreadsheets. **Delete Worksheet** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** from dropdown 3. Choose **Worksheet ID** to delete 4. Configure optional properties: * **Drive**: Specify drive location > ⚠️ **Warning**: Worksheet deletion is permanent. Ensure you have backups of important data before deleting. > πŸ’‘ **Use case**: Remove outdated worksheets, clean up temporary sheets, or delete worksheets when workflows determine they're no longer needed. #### How to Work with Rows **Add Single Row** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Check **"Does the first row of the sheet have a header?"** if applicable 4. If headers exist, select **Values** from dropdown to map data to columns 5. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Header Explanation**: When you indicate the first row has headers, Google Sheets will show you the column names, making it easier to map your data to the correct columns. > πŸ’‘ **Use case**: Add new records to data sheets, append form submissions to spreadsheets, or insert calculated results from workflows. **Add Multiple Rows** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Enter **Row Values** (data for multiple rows) 4. Configure optional properties: * **Drive**: Specify drive location * **Reset Row Format**: Clear existing formatting > πŸ’‘ **Use case**: Batch import data from external sources, add multiple calculated results, or populate spreadsheets with large datasets from workflows. **Update Row** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Enter **Row Number** to specify which row to update 4. Check **"Does the first row of the sheet have a header?"** if applicable 5. Select **Values** from dropdown to specify new data 6. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Use case**: Update existing records with new information, modify calculated values, or synchronize spreadsheet data with external systems. **Upsert Row** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Choose **Insert Cells/Column Values** from dropdown 4. Enter **Key Column** to identify unique records 5. Configure optional properties: * **Drive**: Specify drive location * **Key Values**: Values to match for updates * **Update Column Values**: New data for matched records > πŸ’‘ **Upsert Explanation**: "Upsert" means update if the record exists, or insert if it doesn't. The key column helps identify whether a record already exists. > πŸ’‘ **Use case**: Maintain unique records in spreadsheets, update existing data or add new entries automatically, or synchronize external data while avoiding duplicates. **Update Multiple Rows** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Enter **Range** using A1 notation (e.g., A2:D10) 4. Provide **Row Values** for the specified range 5. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Range Example**: A2:D10 means start at cell A2 and end at cell D10, covering 4 columns and 9 rows of data. > πŸ’‘ **Use case**: Update blocks of data efficiently, refresh calculated ranges, or synchronize multiple records in batch operations. **Find Row** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Enter **Column** to search in 4. Enter **Value** to search for 5. Configure optional properties: * **Drive**: Specify drive location * **Export Row**: Include row data in results (checkbox) > πŸ’‘ **Use case**: Locate specific records in large spreadsheets, find rows matching criteria for updates, or verify data existence before processing. **Delete Rows** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Enter **Start Index** (first row to delete) 4. Configure optional properties: * **Drive**: Specify drive location * **End Index**: Last row to delete (for range deletion) > πŸ’‘ **Use case**: Remove outdated records, clean up temporary data, or delete rows based on workflow conditions. **Clear Rows** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Enter **Start Index** (first row to clear) 4. Configure optional properties: * **Drive**: Specify drive location * **End Index**: Last row to clear > πŸ’‘ **Clear vs Delete**: Clear removes content but keeps the row structure, while delete removes the entire row and shifts others up. > πŸ’‘ **Use case**: Reset data while maintaining structure, clear temporary calculations, or prepare rows for new data input. #### How to Work with Individual Cells **Update Cell** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Enter **Cell** reference using A1 notation (e.g., A1, B5, C10) 4. Enter **Cell Value** (new data for the cell) 5. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Cell Reference Examples**: A1 (first cell), B5 (column B, row 5), Z100 (column Z, row 100) > πŸ’‘ **Use case**: Update specific calculated values, modify individual data points, or set formula results in precise locations. **Get Cell** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Enter **Cell Number** using A1 notation 4. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Use case**: Retrieve specific values for workflow decisions, get calculated results, or extract individual data points for processing. **Clear Cells** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Enter **Cell** reference to clear 4. Configure optional properties: * **Drive**: Specify drive location > πŸ’‘ **Use case**: Reset specific calculations, clear temporary values, or prepare cells for new data input. #### How to Retrieve Data **Get Data from Sheets** 1. Connect your Google Sheets account 2. Select **Spreadsheet ID** and **Worksheet ID** from dropdowns 3. Configure optional properties: * **Drive**: Specify drive location * **Range**: Specify range using A1 notation (e.g., A1:D10, B:B for entire column) > πŸ’‘ **Range Examples**: > > * A1:D10 (rectangular area from A1 to D10) > * A:A (entire column A) > * 1:1 (entire row 1) > * B2:E (from B2 to end of column E) > πŸ’‘ **Use case**: Extract data for analysis, retrieve ranges for processing, or get worksheet content for integration with other systems. ### Understanding Complex Google Sheets Operations **Working with Headers** When a spreadsheet has headers in the first row: * Check the "Does the first row have headers?" checkbox * This reveals column names in dropdowns for easy data mapping * Headers help ensure data goes to the correct columns * Makes it easier to work with structured data **Drive and Folder Organization** * **My Drive** appears as the default option in drive dropdowns * You can organize spreadsheets in specific Google Drive folders * Drive selection affects where new spreadsheets are created * Folder organization helps maintain clean workspace structure **A1 Notation System** Google Sheets uses A1 notation for cell references: * **Single cells**: A1, B5, Z100 * **Ranges**: A1:D10 (rectangle), A:A (entire column), 1:1 (entire row) * **Open ranges**: A1:D (from A1 to end of column D) **Row and Column Indexing** * **Row numbers** start at 1 (first row) * **Column letters** start at A (first column) * **Start Index**: Beginning position for operations * **End Index**: Ending position for range operations ### Important Considerations * Spreadsheet IDs and Worksheet IDs are unique identifiers required for most operations * A1 notation is the standard way to reference cells and ranges in Google Sheets * Header row detection helps with data mapping and organization * Upsert operations combine update and insert functionality for efficient data management * Drive folder selection affects where new files are created and stored * Clear operations remove content while maintaining structure, delete operations remove entire rows/columns * Range operations allow efficient batch processing of multiple cells or rows > ⚠️ **Data Management**: Always verify cell references and ranges before executing operations. Incorrect ranges can overwrite important data. ### How Google Sheets Actions Work in Your Workflow 1. Add the appropriate Sheets action based on your data management needs 2. Connect your Google Sheets account securely 3. Configure required fields (spreadsheet ID, worksheet ID, cell references, etc.) 4. Set optional properties for drive organization and advanced functionality 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the Sheets action will execute the specified operation 7. Spreadsheet data becomes available as variables for subsequent workflow actions ### Common Workflow Patterns **Data Collection and Reporting** * Create new spreadsheets for monthly or project-specific reports * Add rows automatically from form submissions or external data sources * Update existing records with new information from workflows * Generate comprehensive reports using data from multiple sources **Data Processing and Analysis** * Retrieve data from specific ranges for analysis * Update calculated values based on external system changes * Clear and refresh data ranges for new processing cycles * Find and update specific records based on criteria **Spreadsheet Organization and Management** * Create and organize worksheets for different data categories * Copy successful worksheet templates to new projects * Delete outdated worksheets and clean up data structure * Keep worksheet structure tidy and consistent across projects **Integration and Synchronization** * Upsert data to maintain synchronized records with external systems * Update multiple rows efficiently for batch data operations * Retrieve specific cell values for workflow decision making * Clear and prepare spreadsheets for fresh data input > πŸ’‘ **Best Practice**: Use Google Sheets actions to seamlessly integrate spreadsheet operations into your business processes - from automated data collection and reporting to comprehensive data analysis and team collaboration across complex data management workflows. Always use header detection and proper A1 notation for reliable data operations. # Dropbox Dropbox integration in Lleverage enables you to automate file storage, organization, and sharing workflows directly with your Dropbox account. Upload, search, organize, and manage files and folders seamlessly within your automated processes. ### Key Features * **File operations** - Upload single or multiple files, download, delete, and manage file revisions * **Folder management** - Create, rename, move, and organize folder structures * **Search capabilities** - Find files and folders using advanced search criteria and filters * **Text file handling** - Create and append to text files with automated content * **Sharing controls** - Create and update shared links for collaboration * **Version control** - Access file revisions and restore previous versions * **Flexible inputs** - Support for dropdown selections and manual input with variables * **Secure connection** - Direct integration with Dropbox API ### How to Add Dropbox Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Dropbox integration: * Select "External Apps" from the categories * Find "Dropbox" in the top 10 popular integrations, or * Search for "Dropbox" in the provider list 3. Click on Dropbox to view available actions 4. Select your desired Dropbox action from the comprehensive list > πŸ’‘ **Popularity**: Dropbox appears in the top 10 integrations due to its widespread use for file storage and collaboration. ### How to Connect Your Dropbox Account **Initial Setup** 1. Click "Connect Dropbox Account" in any Dropbox action 2. Follow the Dropbox authentication process 3. Grant necessary permissions for file access and management 4. Your connected account will be available across all Dropbox actions > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for the level of file access and management your workflows require. ### How to Configure Dropbox Actions #### How to Upload Files **Upload File** 1. Connect your Dropbox account 2. Select the **Path** (destination folder) from dropdown or input manually 3. Specify the **File Name** for the uploaded file 4. Configure optional properties: * **File Name**: Custom name for the uploaded file * **File Path**: Source path of the file to upload * **Auto Rename**: Automatically rename if file exists (checkbox) * **Mute**: Suppress notifications (checkbox) * **Strict Conflict**: Handle naming conflicts strictly (checkbox) * **Mode**: Choose upload behavior (Add, Overwrite, or Update) > πŸ’‘ **Use case**: Save workflow outputs to Dropbox, upload processed documents, or store generated files in organized folder structures. **Upload Multiple Files** 1. Connect your Dropbox account 2. Select the **Path** (destination folder) from dropdown 3. Choose **Files** to upload (multiple selection) 4. Configure optional properties (same as single file upload): * **File Names**: Custom names for uploaded files * **File Paths**: Source paths of files to upload * **Auto Rename**, **Mute**, **Strict Conflict** checkboxes * **Mode**: Upload behavior for all files > πŸ’‘ **Use case**: Batch upload multiple workflow outputs, transfer entire document sets, or upload collections of processed files efficiently. #### How to Manage Files and Folders **Create Folder** 1. Connect your Dropbox account 2. Enter **Folder Name** for the new folder 3. Configure optional properties: * **Auto Rename**: Automatically rename if folder exists (default: checked) * **Path**: Parent directory location (dropdown or input) > πŸ’‘ **Use case**: Automatically create project folders, organize files into structured hierarchies, or establish storage locations for workflow outputs. **Rename File or Folder** 1. Connect your Dropbox account 2. Select the **Path** of the item to rename (dropdown or input) 3. Enter **New Name** for the file or folder 4. Configure optional properties: * **Auto Rename**: Handle naming conflicts automatically (checkbox) * **Allow Ownership Transfer**: Enable ownership changes (checkbox) > πŸ’‘ **Use case**: Update file names based on processing results, reorganize content with meaningful names, or maintain consistent naming conventions. **Move File or Folder** 1. Connect your Dropbox account 2. Select **Path From** (current location) and **Path To** (destination) 3. Configure optional properties: * **Auto Rename**: Handle naming conflicts (checkbox) * **Allow Ownership Transfer**: Enable ownership changes (checkbox) > πŸ’‘ **Use case**: Organize files based on workflow outcomes, move completed documents to archive folders, or relocate files based on processing status. **Delete File or Folder** 1. Connect your Dropbox account 2. Select the **Path** of the item to permanently remove > ⚠️ **Warning**: This permanently removes files from Dropbox. Ensure you have backups if needed. > πŸ’‘ **Use case**: Clean up temporary files, remove outdated documents, or delete files when workflows determine they're no longer needed. #### How to Search for Content **Search Files and Folders** 1. Connect your Dropbox account 2. Enter **Query** to search for specific files or folders by name 3. Select **Path** to limit search to specific folder (dropdown or input) 4. Configure extensive optional properties: * **Order By**: Sort results (Relevance or Last Modified Time) * **File Status**: Include active, archived, or deleted files * **File Format**: Filter by specific formats (checkbox) * **Category**: Filter by content type (Image, Document, PDF, Spreadsheet, Presentation, Audio, Video, Folder, Paper, Others) * **File Extensions**: Specify particular file types * **Include Highlights**: Show search result highlights (checkbox) * **Limit**: Maximum number of results to return > πŸ’‘ **Use case**: Locate specific documents for processing, find files matching workflow conditions, or retrieve content based on detailed criteria for automated operations. #### How to Work with File Versions **List File Revisions** 1. Connect your Dropbox account 2. Select the **Path** of the file to examine 3. Configure optional properties: * **Mode**: Choose "Path" or "ID" for file identification * **Limit**: Maximum number of revisions to retrieve > πŸ’‘ **Use case**: Audit file changes, retrieve version history for compliance, or access previous versions for workflow processing. **Restore File** 1. Connect your Dropbox account 2. Select the **Path** of the file to restore 3. Choose the **Revision** to restore from dropdown or input > πŸ’‘ **Use case**: Recover accidentally modified files, revert to previous versions based on workflow conditions, or restore files to specific states. #### How to Handle Text Files **Create Text File** 1. Connect your Dropbox account 2. Enter **File Name** for the new text file 3. Select **Path** for the file location (dropdown) 4. Enter **Content** for the file > πŸ’‘ **Use case**: Generate reports in text format, create log files from workflow data, or save processed text content to organized locations. **Create or Append to Text File** 1. Connect your Dropbox account 2. Enter **File Name** for the target file 3. Enter **Content** to add to the file 4. Configure optional properties: * **Path**: File location (creates file if it doesn't exist) > πŸ’‘ **Use case**: Build cumulative log files, append workflow results to existing reports, or maintain running text records across multiple workflow executions. #### How to Manage File Operations **List Files** 1. Connect your Dropbox account 2. Select **Path** of the folder to examine 3. Configure default checkbox options: * **Recursive**: Include subfolders (default: checked) * **Include Deleted**: Show deleted files (default: unchecked) * **Include Has Explicit Shared Members**: Show sharing info (default: unchecked) * **Include Mounted Folders**: Include mounted locations (default: unchecked) * **Include Non-Downloadable Files**: Show all file types (default: checked) 4. Optional properties: * **Limit**: Maximum number of files to return > πŸ’‘ **Use case**: Generate file inventories, audit folder contents, or retrieve file lists for processing or organization workflows. **Download File to Temp** 1. Connect your Dropbox account 2. Select the **Path** of the file to download 3. Configure optional properties: * **File Name**: Custom name for downloaded file > πŸ’‘ **Use case**: Retrieve files for processing in workflows, download documents for analysis, or access Dropbox content for integration with other systems. #### How to Share Content **Create/Update Shared Link** 1. Connect your Dropbox account 2. Select the **Path** of the file or folder to share (dropdown or input) > πŸ’‘ **Use case**: Automatically generate sharing links for workflow outputs, create public access to processed documents, or enable collaboration on workflow-generated content. ### Understanding Input Types **Dropdown vs Manual Input** * **Path fields**: All path selections support both dropdown (showing your Dropbox structure) and manual text input * **Checkboxes/Switches**: Boolean options that can be toggled on or off * **Mode dropdowns**: Predefined options like Add, Overwrite, Update for upload behavior * **Category filters**: Comprehensive content type filtering for searches **Default Settings** * Many checkboxes have sensible defaults (like Auto Rename being checked) * Recursive folder listing is enabled by default for comprehensive results * Include non-downloadable files is checked to show complete file listings > πŸ’‘ **Flexibility**: The combination of dropdown convenience and manual input allows for both user-friendly selection and dynamic workflow-driven values. ### Important Considerations * Path selections support both folder browsing and manual input with variables * Auto-rename options help prevent conflicts when uploading or moving files * File revision tracking enables recovery and version control * Search functionality includes advanced filtering by file type, status, and content category * Text file operations support both creation and appending for flexible content management * Shared link creation enables automated collaboration workflows > ⚠️ **File Management**: Delete operations are permanent. Use move to trash functionality when available, or ensure proper backup procedures. ### How Dropbox Actions Work in Your Workflow 1. Add the appropriate Dropbox action based on your file management needs 2. Connect your Dropbox account securely 3. Configure required fields (paths, file names, content, etc.) 4. Set optional properties for advanced functionality and filtering 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the Dropbox action will execute the specified operation 7. File data and results become available as variables for subsequent workflow actions ### Common Workflow Patterns **Automated File Organization** * Upload workflow outputs to organized folder structures * Create project-specific folders automatically * Move and rename files based on processing results **Document Processing and Storage** * Download files for processing, then upload results * Create text reports and logs from workflow data * Maintain file revision history for compliance and recovery **Content Sharing and Collaboration** * Generate shared links for workflow outputs * Organize shared content in structured folders * Enable team access to processed documents > πŸ’‘ **Best Practice**: Use Dropbox actions to seamlessly integrate cloud storage into your business processes - from automated document processing to organized file management and team collaboration workflows. # Trello Trello integration in Lleverage enables you to automate project management and task organization workflows directly with your Trello boards. Create, update, and manage cards, lists, and boards while handling team collaboration seamlessly within your automated processes. ### Key Features * **Board management** - Create new boards or copy existing ones with custom configurations * **Card operations** - Create, update, move, and archive cards with detailed properties * **List management** - Create, rename, and organize lists within boards * **Label system** - Create, find, and manage labels for card categorization * **Checklist handling** - Create checklists, add items, and complete tasks * **Team collaboration** - Search and manage members across boards * **Advanced search** - Find cards, boards, lists, and labels using specific criteria * **Flexible inputs** - Support for dropdown selections and manual input with variables ### How to Add Trello Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Trello integration: * Select "External Apps" from the categories * Search for "Trello" in the provider list, or * Scroll down to find Trello in the alphabetical list 3. Click on Trello to view available actions 4. Select your desired Trello action from the comprehensive list ### How to Connect Your Trello Account **Initial Setup** 1. Click "Connect Trello Account" in any Trello action 2. Follow the Trello authentication process 3. Grant necessary permissions for board and card access 4. Your connected account will be available across all Trello actions > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for the boards and team functionality your workflows require. ### How to Configure Trello Actions #### How to Manage Boards **Create Board** 1. Connect your Trello account 2. Enter **Name** for the new board 3. Select **Organization ID** from dropdown (if applicable) 4. Configure extensive optional properties: * **Default Labels**: Set up initial label structure * **Default Lists**: Create standard lists automatically * **Description**: Add board description * **Board Source ID**: Copy from existing board * **Keep From Source**: Retain elements from source board * **Power-ups**: Enable board extensions * **Permissions**: Set voting, comments, invitations, self-join, card covers, background, and card aging preferences > πŸ’‘ **Use case**: Automatically create project boards for new initiatives, set up standardized board templates, or establish team workspaces with predefined structures. **Search Boards** 1. Connect your Trello account 2. Enter **Query** to search for specific boards 3. Configure optional properties: * **Organization IDs**: Limit search to specific organizations * **Partial Search**: Enable partial matching * **Board Fields**: Specify which board data to retrieve * **Board Limit**: Control number of results returned > πŸ’‘ **Use case**: Locate boards for automated operations, find project boards based on criteria, or audit board structures across organizations. #### How to Manage Lists **Create List** 1. Connect your Trello account 2. Select **Board ID** from dropdown 3. Enter **Name** for the new list 4. Configure optional properties: * **List Source ID**: Copy from existing list * **Position**: Set list placement on board > πŸ’‘ **Use case**: Automatically create workflow stages, set up project phases, or establish task categories based on workflow conditions. **Rename List** 1. Connect your Trello account 2. Select **Board** from dropdown 3. Choose **List** to rename 4. Enter new **Name** for the list > πŸ’‘ **Use case**: Update list names based on project phases, modify workflow stages dynamically, or maintain current naming conventions. **Find List** 1. Connect your Trello account 2. Select **Board** from dropdown 3. Enter **List Name** to search for 4. Configure **List Filters**: * **All** (default): Show all lists * **Closed**: Show archived lists only * **Open**: Show active lists only > πŸ’‘ **Use case**: Locate specific lists for card operations, verify list existence before automation, or find lists matching naming patterns. **Get List** 1. Connect your Trello account 2. Select **Board** from dropdown 3. Specify **List ID** to retrieve information > πŸ’‘ **Use case**: Get list metadata for workflow decisions, retrieve list properties for processing, or audit list configurations. #### How to Manage Cards **Create Card** 1. Connect your Trello account 2. Select **Board** from dropdown 3. Enter **Name** for the new card 4. Choose **List** where card should be created 5. Configure extensive optional properties: * **Description**: Card details and content * **Position**: Card placement in list * **Due Date** and **Due Complete**: Set deadlines and completion status * **Members**: Assign team members * **Labels**: Apply categorization labels * **File Attachment**: Add files to card * **Copy Card**: Duplicate from existing card * **Address**, **Location**, **Coordinates**: Add location data * **Custom Field IDs**: Set custom field values > πŸ’‘ **Use case**: Automatically create tasks from form submissions, generate cards from workflow triggers, or set up project tasks with complete details and assignments. **Update Card** 1. Connect your Trello account 2. Select **Board** and **Card** from dropdowns 3. Configure optional properties to modify: * **Name**: Change card title * **Description**: Update card details * **Archive**: Archive or unarchive card * **Members**: Modify team assignments * **Cover**: Update card cover image * **Attachment ID**: Manage card attachments * **List**: Move card to different list * **Labels**: Update categorization * **Position**: Change card order * **Due Date** and **Due Complete**: Modify deadlines * **Subscribed**: Change notification settings * **Address**, **Location**, **Coordinates**: Update location data * **Custom Field IDs**: Modify custom fields > πŸ’‘ **Use case**: Update task progress, modify card details based on workflow processing, or synchronize external data with Trello cards. **Get Card** 1. Connect your Trello account 2. Select **Board** and **Card** from dropdowns 3. Configure optional properties: * **Custom Field Items**: Include custom field data (checkbox) > πŸ’‘ **Use case**: Retrieve card information for workflow decisions, get current task status, or extract card data for reporting. **Move Card to List** 1. Connect your Trello account 2. Select **Board**, **Card**, and target **List** from dropdowns > πŸ’‘ **Use case**: Automate task progression through workflow stages, move cards based on completion status, or organize tasks by current phase. **Archive Card** 1. Connect your Trello account 2. Select **Board** and **Card** from dropdowns > πŸ’‘ **Use case**: Clean up completed tasks, archive outdated cards, or remove cards when workflows determine they're no longer needed. #### How to Search Content **Search Cards** 1. Connect your Trello account 2. Enter **Query** to search for specific cards 3. Configure optional properties: * **Boards**: Limit search to specific boards * **Partial Search**: Enable partial matching * **Card Fields**: Specify which card data to retrieve (All, Badges, Due Amount, etc.) * **Card Limit**: Control number of results returned > πŸ’‘ **Use case**: Find tasks matching specific criteria, locate cards for automated processing, or retrieve cards based on content or properties. **Search Members** 1. Connect your Trello account 2. Enter **Search Query** to find team members 3. Configure optional properties: * **Board ID**: Limit search to specific board members * **Organization ID**: Search within organization * **Limit**: Control number of results > πŸ’‘ **Use case**: Find team members for card assignments, locate users for board permissions, or search team directory for automated notifications. #### How to Manage Labels **Create Label** 1. Connect your Trello account 2. Select **Board ID** from dropdown 3. Enter **Name** for the label 4. Choose **Color** from dropdown options: * Yellow, Purple, Blue, Red, Green, Orange, Black, Sky, Pink, Lime, or Null > πŸ’‘ **Use case**: Create project-specific labels, establish categorization systems, or set up labels for automated card organization. **Find Label** 1. Connect your Trello account 2. Select **Board** from dropdown 3. Set **Limit** for results (default: 50) 4. Configure optional properties: * **Label Name**: Search for specific label > πŸ’‘ **Use case**: Locate labels for card assignment, verify label existence before automation, or audit labeling systems. **Remove Card Labels** 1. Connect your Trello account 2. Select **Board**, **Card**, and **Label** from dropdowns > πŸ’‘ **Use case**: Clean up card categorization, remove outdated labels, or modify card organization based on workflow changes. #### How to Manage Checklists **Create Checklist Item** 1. Connect your Trello account 2. Select **Board**, **Card**, and **Checklist ID** from dropdowns 3. Enter **Name** for the checklist item 4. Configure optional properties: * **Position**: Set item order in checklist * **Checked**: Set initial completion status > πŸ’‘ **Use case**: Add subtasks to cards automatically, create detailed task breakdowns, or populate checklists based on workflow requirements. **Complete Checklist Item** 1. Connect your Trello account 2. Select **Board**, **Card**, **Checklist**, and **Checklist Item ID** from dropdowns > πŸ’‘ **Use case**: Mark subtasks as complete based on workflow progress, automate checklist completion, or update task status from external systems. **Search Checklist** 1. Connect your Trello account 2. Select **Type**: Board or Card 3. Enter **Query** to find specific checklists > πŸ’‘ **Use case**: Locate checklists for automated updates, find task templates, or search for specific checklist content. **Delete Checklist** 1. Connect your Trello account 2. Select **Board**, **Card**, and **Checklist** from dropdowns > πŸ’‘ **Use case**: Remove completed checklists, clean up card organization, or delete outdated task lists based on workflow conditions. ### Understanding Dropdown Behavior **No Options Available** * When dropdowns don't contain relevant data, you'll see "No options available" as placeholder text * This applies to all Trello integrations and indicates no matching content in your account * You can still input values manually or use workflow variables **Hierarchical Selection** * Board selection affects available lists and cards in subsequent dropdowns * List selection determines available cards within that list * This hierarchical relationship helps maintain data consistency > πŸ’‘ **Flexibility**: All dropdown fields also accept manual input and workflow variables for dynamic automation. ### Important Considerations * Board, list, and card dropdowns populate based on your Trello account access * Label colors are predefined by Trello's system * Checklist operations require existing checklists on cards * Custom fields require board-level custom field setup * Position parameters control ordering within lists and boards * Archive operations preserve data while removing from active view > ⚠️ **Permissions**: Ensure your Trello account has appropriate permissions for the boards and teams you want to access through workflows. ### How Trello Actions Work in Your Workflow 1. Add the appropriate Trello action based on your project management needs 2. Connect your Trello account securely 3. Configure required fields (boards, cards, lists, etc.) 4. Set optional properties for advanced functionality 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the Trello action will execute the specified operation 7. Board and card data become available as variables for subsequent workflow actions ### Common Workflow Patterns **Automated Project Setup** * Create boards with standardized lists and labels * Generate cards from external triggers or form submissions * Set up team assignments and due dates automatically **Task Management and Progression** * Move cards through workflow stages based on completion status * Update card details from external system changes * Complete checklist items based on automated processes **Team Collaboration and Reporting** * Search for cards and boards to generate progress reports * Assign team members based on workflow conditions * Update project status across multiple boards > πŸ’‘ **Best Practice**: Use Trello actions to seamlessly integrate project management into your business processes - from automated task creation to progress tracking and team coordination workflows. # Asana Asana integration in Lleverage enables you to automate project management and task coordination workflows directly with your Asana workspace. Create, update, and organize tasks, projects, and teams while maintaining collaboration and progress tracking seamlessly within your automated processes. ### Key Features * **Task management** - Create, update, and organize tasks with detailed properties and assignments * **Project operations** - Create projects, search existing ones, and manage project structure * **Team collaboration** - Assign tasks, add comments, and manage team workflows * **Hierarchical organization** - Work with workspaces, projects, sections, and subtasks * **Advanced search** - Find tasks, projects, and sections using specific criteria * **Template support** - Create tasks from predefined templates * **Flexible assignments** - Manage assignees, followers, and access levels * **Custom fields** - Support for custom data and project-specific information ### Key Asana Concepts **Understanding Asana Structure** * **Workspace**: Top-level container for your organization's work * **Project**: Collection of related tasks and sections within a workspace * **Section**: Organizational category within a project (like columns in a board) * **Task**: Individual work item with details, assignments, and due dates * **Subtask**: Smaller task that belongs to a parent task * **GID**: Global Identifier - Asana's unique ID system for all objects * **Assignee**: Team member responsible for completing a task * **Followers**: Team members who receive updates about a task without being responsible * **Notes**: Detailed descriptions and additional context for tasks or projects ### How to Add Asana Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Asana integration: * Select "External Apps" from the categories * Search for "Asana" in the provider list, or * Scroll down to find Asana in the alphabetical list 3. Click on Asana to view available actions 4. Select your desired Asana action from the comprehensive list ### How to Connect Your Asana Account **Initial Setup** 1. Click "Connect Asana Account" in any Asana action 2. Follow the Asana authentication process 3. Grant necessary permissions for workspace and project access 4. Your connected account will be available across all Asana actions > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for the workspaces and projects your workflows need to access. ### How to Configure Asana Actions #### How to Manage Tasks **Create Task** 1. Connect your Asana account 2. Select **Workspace** from dropdown 3. Choose **Project** where the task should be created 4. Enter **Name** for the new task 5. Configure extensive optional properties: * **Tags**: Categorize the task with labels * **Assignee**: Assign responsibility to a team member * **Assignee Section**: Specify which section to place the task * **Completed**: Set initial completion status * **Due At**: Set deadline for task completion * **Followers**: Add team members to receive updates * **HTML Notes**: Rich text description and details * **Notes**: Plain text task description * **Parent**: Create as subtask of another task * **Start On**: Set task start date * **Custom Fields**: Add project-specific data > πŸ’‘ **Use case**: Automatically create tasks from form submissions, generate work items from workflow triggers, or set up project tasks with complete details and team assignments. **Update Task** 1. Connect your Asana account 2. Select **Workspace** and **Project** from dropdowns 3. Choose **Task GID** to identify the specific task 4. Enter new **Name** if changing task title 5. Configure optional properties: * **Assignee**: Change task ownership * **Assignee Section**: Move to different section * **Completed**: Mark task as done or pending * **Due At**: Modify deadline * **HTML Notes**: Update rich text description * **Start On**: Change start date * **Custom Fields**: Update project-specific data > πŸ’‘ **Use case**: Update task progress based on external system changes, modify assignments when team roles change, or synchronize task status with workflow completion. **Get Task** 1. Connect your Asana account 2. Select **Workspace** and **Project** from dropdowns 3. Choose **Task GID** to retrieve specific task information > πŸ’‘ **Use case**: Retrieve current task details for workflow decisions, get task status for reporting, or extract task data for integration with other systems. **Create Subtask** 1. Connect your Asana account 2. Select **Workspace**, **Project**, and **Task GID** (parent task) 3. Enter **Name** for the subtask 4. Configure optional properties: * **Assignee**: Assign subtask responsibility * **Assignee Section**: Specify section placement * **Completed**: Set initial completion status * **Followers**: Add team members for updates * **HTML Notes**: Rich text subtask description * **Notes**: Plain text description * **Start On**: Set subtask start date * **Tasks**: Link to related tasks > πŸ’‘ **Use case**: Break down complex tasks into manageable pieces, create detailed task hierarchies automatically, or generate subtasks based on workflow requirements. #### How to Search Content **Search Tasks** 1. Connect your Asana account 2. Select **Workspace** from dropdown 3. Enter **Name** to search for specific tasks 4. Configure optional properties: * **Project**: Limit search to specific project * **Assignee**: Find tasks assigned to specific person * **Section**: Search within particular section * **Completed Since**: Find recently completed tasks * **Modified Since**: Find recently updated tasks > πŸ’‘ **Use case**: Locate tasks for automated updates, find work items matching specific criteria, or audit task completion across projects. **Find Task by ID** 1. Connect your Asana account 2. Select **Workspace** and **Project** from dropdowns 3. Enter **Task GID** to locate specific task > πŸ’‘ **Use case**: Retrieve specific tasks using external references, locate tasks from API calls, or find tasks using stored identifiers. **Search Projects** 1. Connect your Asana account 2. Configure optional properties: * **Name**: Search for projects by name * **Workspace**: Limit to specific workspace * **Archived**: Include or exclude archived projects > πŸ’‘ **Use case**: Find projects for task creation, locate project containers for workflow operations, or audit project structures across workspaces. **Search Sections** 1. Connect your Asana account 2. Select **Workspace** and **Project** from dropdowns 3. Enter **Name** to find specific sections within the project > πŸ’‘ **Use case**: Locate sections for task placement, verify section existence before automation, or organize tasks within project structure. #### How to Manage Projects **Create Project** 1. Connect your Asana account 2. Select **Workspace** and **Team** from dropdowns 3. Enter **Name** and **Notes** for the new project 4. Configure extensive optional properties: * **Color**: Set project color coding * **Layout**: Choose project view format * **Default View**: Set initial display mode * **Privacy Settings**: Control project visibility * **Archived**: Set archive status * **Due On**: Set project completion deadline * **Start On**: Set project start date * **Followers**: Add team members for updates * **HTML Notes**: Rich text project description * **Owners**: Assign project leadership * **Default Access Level**: Set team member permissions * **Minimum Access Level for Customization**: Control who can modify * **Minimum Access Level for Sharing**: Control sharing permissions (Admin/Editor options) > πŸ’‘ **Use case**: Automatically create projects for new initiatives, set up standardized project templates, or establish team workspaces with predefined permissions and structure. **Get List of User Projects** 1. Connect your Asana account 2. Select **Workspace** and **User** from dropdowns 3. Retrieves all projects accessible to the specified user > πŸ’‘ **Use case**: Audit user project access, generate project lists for reporting, or identify available projects for task assignment. **Get Tasks from Project** 1. Connect your Asana account 2. Select **Workspace** and **Project** from dropdowns 3. Retrieves a comprehensive list of all tasks within the project > πŸ’‘ **Use case**: Generate project status reports, analyze task distribution, or extract project data for external processing. #### How to Manage Task Organization **Add Task to Section** 1. Connect your Asana account 2. Select **Workspace**, **Project**, **Task**, and **Section GID** 3. Configure optional properties: * **Insert Before**: Position task before specific task * **Insert After**: Position task after specific task > ⚠️ **Important**: This action removes the task from other sections in the project, ensuring tasks belong to only one section at a time. > πŸ’‘ **Use case**: Organize tasks by workflow stage, move tasks through project phases, or categorize work items based on processing status. #### How to Add Task Details **Create Task from Template** 1. Connect your Asana account 2. Select **Workspace**, **Project**, and **Task Template** from dropdowns 3. Configure optional properties: * **Name**: Override template name if needed > πŸ’‘ **Use case**: Standardize task creation with predefined templates, ensure consistent task structure across projects, or rapidly create tasks with established formats. **Create Task Comment** 1. Connect your Asana account 2. Select **Workspace**, **Project**, and **Task GID** 3. Configure optional properties: * **Text**: Plain text comment content * **HTML Text**: Rich formatted comment * **Is Pinned**: Make comment prominent * **Sticker Name**: Add reaction sticker > πŸ’‘ **Use case**: Add automated progress updates, provide workflow status comments, or log system-generated information on tasks. ### Understanding Access Levels **Project Permission Structure** * **Admin**: Full control including project deletion and permission changes * **Editor**: Can modify project content, tasks, and settings * **Minimum Access Levels**: Control what permissions are required for specific actions * **Default Access**: Standard permission level for new team members **Task Assignment Concepts** * **Assignee**: Primary person responsible for task completion * **Followers**: Team members who receive notifications without responsibility * **Assignee Section**: Specific project section where assigned tasks appear ### Important Considerations * GID (Global Identifier) is Asana's unique ID system used to reference all objects * Workspaces contain projects, which contain sections and tasks * Tasks can have subtasks, creating hierarchical work breakdown * Adding tasks to sections removes them from other sections automatically * Custom fields provide project-specific data structure * Access levels control team collaboration and project permissions * Templates enable standardized task creation across projects > ⚠️ **Organization**: Moving tasks between sections removes them from other sections. Plan your project structure accordingly. ### How Asana Actions Work in Your Workflow 1. Add the appropriate Asana action based on your project management needs 2. Connect your Asana account securely 3. Configure required fields (workspace, project, task details, etc.) 4. Set optional properties for advanced functionality and team collaboration 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the Asana action will execute the specified operation 7. Task and project data become available as variables for subsequent workflow actions ### Common Workflow Patterns **Automated Project Setup** * Create projects with predefined structure and team assignments * Generate tasks from external triggers with complete details * Set up standardized workflows using templates **Task Management and Progression** * Update task status based on external system changes * Move tasks through project sections as work progresses * Create subtasks automatically for complex work breakdown **Team Collaboration and Reporting** * Add automated comments to track workflow progress * Assign tasks based on team availability or expertise * Generate project reports using task and progress data > πŸ’‘ **Best Practice**: Use Asana actions to seamlessly integrate project management into your business processes - from automated task creation to progress tracking and team coordination across complex project hierarchies. # Notion Notion integration in Lleverage enables you to automate knowledge management, documentation, and database workflows directly with your Notion workspace. Create, update, and organize pages and databases while maintaining content structure and team collaboration seamlessly within your automated processes. ### Key Features * **Page management** - Create, update, duplicate, and organize Notion pages with rich content * **Database operations** - Query databases, retrieve content, and manage structured data * **Content handling** - Work with blocks, markdown, and various media types * **Search capabilities** - Find pages and databases using advanced search criteria * **Property management** - Handle page properties and database schemas * **Team collaboration** - Add comments and manage page discussions * **Flexible content** - Support for text, lists, media, and structured data blocks * **Hierarchical organization** - Work with parent-child page relationships ### Key Notion Concepts **Understanding Notion Structure** * **Page**: Fundamental content unit in Notion - can contain text, media, databases, and other blocks * **Database**: Structured collection of pages with properties (like a spreadsheet with rich content) * **Block**: Individual content element within a page (text paragraph, heading, image, list item, etc.) * **Property**: Data field in a database (text, number, date, select, etc.) * **Schema**: Structure definition of a database including all its properties and types * **Parent**: Container page that holds child pages or blocks * **Query**: Filter and search criteria used to retrieve specific database content * **Metadata**: Additional information about pages including creation date, last edited, etc. **Content Types** * **Text blocks**: Paragraphs, headings, quotes, and formatted text * **List blocks**: Bulleted lists, numbered lists, and to-do lists * **Media blocks**: Images, videos, files, and embedded content * **Database items**: Individual records within a Notion database ### How to Add Notion Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Notion integration: * Select "External Apps" from the categories * Search for "Notion" in the provider list, or * Scroll down to find Notion in the alphabetical list 3. Click on Notion to view available actions 4. Select your desired Notion action from the comprehensive list ### How to Connect Your Notion Account **Initial Setup** 1. Go to **Settings > Connections** in your project 2. Pick Notion from the list of apps 3. Choose which actions the connection should allow and who should have access (shared or personal) 4. Choose "Connect Now" and sign in to Notion, granting access to the pages and databases your workflows need, or send an authentication link so a colleague can connect on your behalf 5. Your connected account will be available across all Notion actions > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for the workspaces, pages, and databases your workflows need to access. ### How to Configure Notion Actions #### How to Manage Pages **Create Page** 1. Connect your Notion account 2. Select **Parent Page ID** from dropdown (where the new page will be created) 3. Enter **Page Title** for the new page 4. Add **Page Content** (text, blocks, or markdown) 5. Configure optional properties: * **Page Title**: Modify the title (already selected by default) * **Metadata Types**: Add creation and modification metadata * **Page Content**: Enhanced content options (already selected by default) > πŸ’‘ **Use case**: Automatically create documentation pages, generate project pages from templates, or establish knowledge base articles from workflow data. **Update Page** 1. Connect your Notion account 2. Select **Parent Database ID** and **Page ID** from dropdowns 3. Configure optional properties: * **Archive**: Archive or unarchive the page * **Page Metadata Types**: Update page metadata * **Property Types**: Modify page properties > πŸ’‘ **Use case**: Update documentation based on system changes, modify page properties from external data, or archive completed project pages automatically. **Duplicate Page** 1. Connect your Notion account 2. Select **Page ID** to duplicate from dropdown 3. Choose **Parent Page ID** where the copy should be created 4. Configure optional properties: * **Page Title**: Custom title for the duplicated page > πŸ’‘ **Use case**: Create page templates for recurring projects, duplicate successful project structures, or generate standardized documentation formats. **Delete Page** 1. Connect your Notion account 2. Select **Page ID** to remove from dropdown > ⚠️ **Warning**: This permanently removes the page and all its content. Ensure you have backups if needed. > πŸ’‘ **Use case**: Clean up outdated documentation, remove temporary pages, or delete pages when workflows determine they're no longer needed. #### How to Search and Find Content **Find Page or Database** 1. Connect your Notion account 2. Enter **Query** to search for specific pages or databases 3. Specify **Title** for more targeted search 4. Configure optional properties: * **Sort Direction**: Order results ascending or descending * **Page Size**: Control number of results returned * **Start Cursor**: Pagination starting point (Page ID) * **Page or Database**: Filter by content type > πŸ’‘ **Use case**: Locate pages for automated updates, find databases for content integration, or search knowledge base for relevant documentation. **Find Page** 1. Connect your Notion account 2. Configure optional properties for refined search: * **Page Title**: Search by specific title * **Sort Direction**: Control result ordering * **Page Size**: Limit number of results * **Start Cursor**: Pagination control (Page ID) > πŸ’‘ **Use case**: Locate specific pages for workflow operations, find pages matching naming patterns, or audit page structure across workspace. #### How to Retrieve Content and Data **Retrieve Page Metadata** 1. Connect your Notion account 2. Select **Page ID** from dropdown to get detailed page information > πŸ’‘ **Use case**: Get page creation dates for reporting, retrieve page properties for workflow decisions, or audit page metadata for compliance. **Retrieve Page Content** 1. Connect your Notion account 2. Select **Page ID** from dropdown 3. Configure optional properties: * **Retrieve Children**: Include nested blocks and content * **Retrieve as Markdown**: Get content in markdown format instead of blocks > πŸ’‘ **Use case**: Extract page content for processing, convert Notion pages to other formats, or analyze page content for workflow decisions. **Retrieve Page Properties** 1. Connect your Notion account 2. Select **Page ID** and **Property ID** from dropdowns 3. Gets specific property data for the selected page > πŸ’‘ **Use case**: Extract specific data fields from database pages, get property values for workflow conditions, or retrieve structured data for integration. #### How to Work with Databases **Retrieve Database Content** 1. Connect your Notion account 2. Select **Database ID** from dropdown to get all database records > πŸ’‘ **Use case**: Export database content for reporting, synchronize Notion data with external systems, or analyze database records for workflow processing. **Retrieve Data by Schema** 1. Connect your Notion account 2. Select **Database ID** from dropdown 3. Gets the property schema (structure definition) of the database > πŸ’‘ **Schema Explanation**: A schema defines the structure of your database - what properties (columns) it has, their data types (text, number, date, etc.), and any constraints or options. > πŸ’‘ **Use case**: Understand database structure before data operations, validate data types for integration, or audit database configurations across workspace. **Query Database** 1. Connect your Notion account 2. Select **Database ID** from dropdown 3. Enter **Filter** criteria to specify which records to retrieve > πŸ’‘ **Query Explanation**: Queries use filter conditions to retrieve specific database records - like finding all tasks assigned to a person, or all projects with a specific status. > πŸ’‘ **Use case**: Retrieve filtered database records for processing, find specific data matching criteria, or generate reports from database subsets. #### How to Add Content and Comments **Append Blocks to Parent** 1. Connect your Notion account 2. Select **Parent Block ID** from dropdown 3. Choose **Block Types** from dropdown options: * **Append Existing Blocks**: Add pre-existing blocks * **Provide Markdown Content**: Create new blocks from markdown * **Provide Image URL**: Create new image blocks from URLs > πŸ’‘ **Block Explanation**: Blocks are individual content elements - paragraphs, headings, images, lists, etc. This action adds new content to existing pages. > πŸ’‘ **Use case**: Add automated content to documentation pages, append workflow results to project pages, or insert dynamic content based on external data. **Create Comment** 1. Connect your Notion account 2. Enter **Comment** text content 3. Configure optional properties: * **Page ID**: Associate comment with specific page * **Discussion ID**: Add to existing discussion thread > πŸ’‘ **Use case**: Add automated progress updates to project pages, log workflow events as comments, or provide system-generated feedback on documentation. ### Integration Examples and Workflow Patterns **Automated Documentation Workflow** ``` 1. Create Page β†’ Set up new project documentation 2. Append Blocks to Parent β†’ Add standardized sections 3. Update Page β†’ Modify properties based on project data 4. Create Comment β†’ Log project milestones ``` **Database Synchronization Pattern** ``` 1. Query Database β†’ Find records matching criteria 2. Retrieve Page Properties β†’ Get current data values 3. Update Page β†’ Synchronize with external system data 4. Create Comment β†’ Log synchronization events ``` **Knowledge Base Management** ``` 1. Find Page or Database β†’ Locate existing documentation 2. Retrieve Page Content β†’ Extract current content 3. Append Blocks to Parent β†’ Add new information 4. Duplicate Page β†’ Create templates for similar topics ``` **Project Management Integration** ``` 1. Create Page β†’ New project documentation 2. Retrieve Database Content β†’ Get project tasks 3. Query Database β†’ Filter tasks by status 4. Update Page β†’ Reflect current project status ``` ### Important Considerations * Page IDs and Database IDs are unique identifiers required for most operations * Parent-child relationships determine page hierarchy and organization * Blocks are the building units of page content (text, images, lists, etc.) * Database schemas define the structure and data types of your databases * Queries enable filtered retrieval of database content using specific criteria * Markdown support allows easy content creation and formatting * Comments enable team collaboration and workflow logging > ⚠️ **Content Structure**: Understanding Notion's block-based content system is crucial for effective automation. Plan your content structure before implementing workflows. ### How Notion Actions Work in Your Workflow 1. Add the appropriate Notion action based on your knowledge management needs 2. Connect your Notion account securely 3. Configure required fields (page IDs, database IDs, content, etc.) 4. Set optional properties for advanced functionality 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the Notion action will execute the specified operation 7. Page and database data become available as variables for subsequent workflow actions ### Common Workflow Patterns **Automated Knowledge Management** * Create documentation pages from project data * Update pages based on external system changes * Synchronize databases with external data sources * Generate reports from database queries **Content Creation and Organization** * Duplicate page templates for consistent formatting * Append dynamic content to existing pages * Create hierarchical page structures automatically * Manage content lifecycle through page properties **Team Collaboration and Tracking** * Add automated comments for progress tracking * Update page metadata for project status * Query databases for team reporting * Maintain collaborative documentation workflows > πŸ’‘ **Best Practice**: Use Notion actions to seamlessly integrate knowledge management into your business processes - from automated documentation creation to data synchronization and collaborative content management across complex organizational structures. # ClickUp ClickUp integration in Lleverage enables you to automate project management and task tracking workflows directly with your ClickUp workspace. Manage tasks, spaces, lists, and team collaboration while maintaining productivity tracking and project organization seamlessly within your automated processes. ### Key Features * **Task management** - Create, update, and organize tasks with custom fields and properties * **Time tracking** - Start and stop time entries for automated productivity monitoring * **Project organization** - Manage spaces, lists, and folders within your workspace hierarchy * **Team collaboration** - Handle comments, assignees, and team coordination * **Checklist operations** - Create and manage task checklists and checklist items * **View management** - Work with custom views and retrieve view-specific data * **Custom fields** - Support for project-specific data and custom task properties * **Flexible filtering** - Advanced filtering options using folder and list structures ### Key ClickUp Concepts **Understanding ClickUp Structure** * **Workspace**: Top-level container for your organization's projects and teams * **Space**: Major project area or department within a workspace (like "Marketing" or "Development") * **Folder**: Organizational container within a space for grouping related lists * **List**: Collection of related tasks, similar to a project or category * **Task**: Individual work item with details, assignments, and tracking * **View**: Custom display configuration for tasks (board, list, calendar, etc.) * **Custom Fields**: Additional data fields specific to your workflow needs * **Time Entry**: Time tracking record associated with tasks or projects * **Checklist**: Sub-tasks or steps within a main task * **Priority**: Task importance level (urgent, high, normal, low) **Team and Permission Concepts** * **Assignees**: Team members responsible for task completion * **Authorized Team**: Team members with permission to access specific content * **Custom Task IDs**: Unique identifiers for tasks beyond ClickUp's default system ### How to Add ClickUp Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to ClickUp integration: * Select "External Apps" from the categories * Search for "ClickUp" in the provider list, or * Scroll down to find ClickUp in the alphabetical list 3. Click on ClickUp to view available actions 4. Select your desired ClickUp action from the comprehensive list ### How to Connect Your ClickUp Account **Initial Setup** 1. Click "Connect ClickUp Account" in any ClickUp action 2. Follow the ClickUp authentication process 3. Grant necessary permissions for workspace and task access 4. Your connected account will be available across all ClickUp actions > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for the workspaces and teams your workflows need to access. ### Understanding Filter List ID by Folder **Hierarchical Filtering System** When you enable "Filter List ID by Folder" checkbox, ClickUp provides structured dropdown options: * **Folder ID**: Choose specific folder within the space * **List ID**: Select list within the chosen folder * **Task**: Pick specific task within the list * **Checklist**: Choose checklist within the task * **Checklist Item**: Select specific checklist item > πŸ’‘ **Linear Process**: ClickUp follows a hierarchical structure - select workspace first, then space, then use filtering to navigate deeper into your project structure. ### How to Configure ClickUp Actions #### How to Manage Tasks **Update Task** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Configure optional properties: * **Use Custom Task IDs**: Enable custom task identification * **Authorized Team**: Set team access permissions * **Name**: Update task title * **Description**: Modify task details * **Priority**: Set task importance (urgent, high, normal, low) * **Assignees**: Assign team members * **Due Date**: Set task deadline * **Start Time**: Set task start date * **Filter List ID by Folder**: Use hierarchical filtering > πŸ’‘ **Use case**: Update task progress based on external system changes, modify assignments when team roles change, or synchronize task status with workflow completion. **Get Task** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Enable **Filter List ID by Folder** checkbox for hierarchical selection 4. Configure optional properties: * **Use Custom Task IDs**: Enable custom identification system * **Authorized Team**: Specify team access requirements > πŸ’‘ **Use case**: Retrieve current task details for workflow decisions, get task status for reporting, or extract task data for integration with other systems. **Get Tasks** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Enable **Filter List ID by Folder** checkbox for targeted task retrieval 4. Configure optional properties: * **Archived**: Include or exclude archived tasks * **Page**: Control pagination for large task lists * **Order By**: Sort tasks by specific criteria * **Assignees**: Filter by assigned team members > πŸ’‘ **Use case**: Generate task lists for reporting, retrieve tasks matching specific criteria, or analyze project progress across multiple lists. #### How to Manage Project Structure **Update Space** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Enter new **Name** for the space 4. Configure **Private** setting to control space visibility > πŸ’‘ **Use case**: Reorganize project structure, update space names for clarity, or modify privacy settings based on team changes. **Update List** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Enter new **Name** for the list 4. Enable **Filter List ID by Folder** for specific list targeting 5. Configure optional properties: * **Content**: Update list description * **Priority**: Set default priority for list tasks * **Assignees**: Set default assignees for new tasks > πŸ’‘ **Use case**: Maintain current project organization, update list names for project phases, or modify list settings based on workflow requirements. **Update Folder** 1. Connect your ClickUp account 2. Select **Workspace**, **Space**, and **Folder** from dropdowns 3. Enter new **Name** for the folder 4. Configure **Hidden** checkbox to control folder visibility > πŸ’‘ **Use case**: Reorganize project hierarchy, update folder names for clarity, or hide completed project folders while preserving data. **Get Spaces** 1. Connect your ClickUp account 2. Select **Workspace** from dropdown 3. Configure optional properties: * **Archived**: Include archived spaces in results > πŸ’‘ **Use case**: Audit workspace organization, retrieve available spaces for task creation, or generate workspace structure reports. #### How to Handle Time Tracking **Start Time Entry** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Enter **Description** for the time entry 4. Configure optional properties: * **Use Custom Task IDs**: Link to specific task using custom IDs * **Authorized Team**: Set team access for time entry * **Filter List ID by Folder**: Associate with specific task > πŸ’‘ **Use case**: Automatically start time tracking when workflows begin, log time for automated processes, or track time spent on specific workflow operations. **Stop Time Entry** 1. Connect your ClickUp account 2. Select **Workspace** from dropdown 3. Stops the currently active time entry > πŸ’‘ **Use case**: End time tracking when workflows complete, stop timers automatically based on task completion, or manage time tracking for automated processes. #### How to Manage Comments and Communication **Update Comment** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Enable **Filter List ID by Folder** to target specific comments 4. Configure optional properties: * **Comment Text**: Update comment content * **Assignees**: Modify comment assignees * **Resolved**: Mark comment as resolved > πŸ’‘ **Use case**: Update automated status comments, modify progress reports, or resolve comments based on workflow completion. **Get Task Comments** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Configure optional properties: * **Use Custom Task IDs**: Filter by custom task identification * **Authorized Team**: Limit to team-accessible comments * **Filter List ID by Folder**: Target specific task comments > πŸ’‘ **Use case**: Retrieve comment history for analysis, extract feedback for workflow decisions, or monitor team communication on specific tasks. #### How to Work with Checklists **Update Checklist** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Enter new **Name** for the checklist 4. Enable **Filter List ID by Folder** for specific targeting 5. Configure optional properties: * **Use Custom Task IDs**: Enable custom task identification * **Authorized Team**: Set team access permissions * **Position**: Control checklist order within task > πŸ’‘ **Use case**: Update checklist names for clarity, reorganize task subtasks, or modify checklist structure based on workflow changes. **Update Checklist Item** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Enter new **Name** for the checklist item 4. Enable **Filter List ID by Folder** to access the full hierarchy 5. Configure optional properties: * **Use Custom Task IDs**: Custom identification system * **Authorized Team**: Team access control * **Assignee**: Assign checklist item to team member * **Resolved**: Mark item as complete * **Checklist Parent**: Link to parent checklist > πŸ’‘ **Use case**: Update subtask details, mark checklist items complete based on workflow progress, or assign specific subtasks to team members. #### How to Work with Views **Get View** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Configure optional properties: * **Filter List ID by Folder**: Target specific view content > πŸ’‘ **Use case**: Retrieve custom view configurations for reporting, analyze view settings for workflow optimization, or audit project display preferences. **Get View Tasks** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Configure optional properties: * **Page**: Control pagination for large result sets * **Filter List ID by Folder**: Target specific view tasks > πŸ’‘ **Use case**: Retrieve tasks from custom views for processing, generate reports based on view configurations, or analyze task organization across different view types. **Get View Comments** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Configure optional properties: * **Filter List ID by Folder**: Target comments from specific views > πŸ’‘ **Use case**: Extract comments from specific project views, analyze communication patterns, or monitor feedback within custom view configurations. **Get Team Views** 1. Connect your ClickUp account 2. Select **Workspace** from dropdown 3. Retrieves all team-accessible views within the workspace > πŸ’‘ **Use case**: Audit team view configurations, identify available views for workflow integration, or analyze team collaboration patterns. #### How to Handle Custom Fields **Remove Task Custom Field** 1. Connect your ClickUp account 2. Select **Workspace** and **Space** from dropdowns 3. Enable **Filter List ID by Folder** to target specific task 4. Configure optional properties: * **Use Custom Task IDs**: Custom identification system * **Authorized Team**: Team access permissions > πŸ’‘ **Use case**: Clean up task data by removing outdated custom fields, modify task structure based on workflow changes, or standardize tasks across projects. **Get Task Templates** 1. Connect your ClickUp account 2. Select **Workspace** from dropdown 3. Configure optional properties: * **Page**: Control template list pagination > πŸ’‘ **Use case**: Retrieve available task templates for automated task creation, analyze template usage across workspace, or standardize task creation processes. ### Important Considerations * ClickUp follows a strict hierarchy: Workspace β†’ Space β†’ Folder β†’ List β†’ Task * Filter List ID by Folder provides access to the complete project hierarchy * Custom Task IDs enable integration with external systems * Time entries can be associated with specific tasks for detailed tracking * Views provide customized displays of task data with specific filtering * Authorized Team settings control access permissions for different content * Priority levels help organize tasks by importance and urgency > ⚠️ **Hierarchy Navigation**: Always select workspace and space before using filtering options. The hierarchical structure must be followed for proper data access. ### How ClickUp Actions Work in Your Workflow 1. Add the appropriate ClickUp action based on your project management needs 2. Connect your ClickUp account securely 3. Configure required fields (workspace, space, task details, etc.) 4. Use Filter List ID by Folder for hierarchical content targeting 5. Set optional properties for advanced functionality and team collaboration 6. Connect the action to other workflow steps as needed 7. When the workflow runs, the ClickUp action will execute the specified operation 8. Task and project data become available as variables for subsequent workflow actions ### Common Workflow Patterns **Automated Task Management** * Update tasks based on external system changes * Start and stop time tracking automatically * Retrieve task data for progress reporting * Manage task assignments based on workflow conditions **Project Organization and Reporting** * Update project structure (spaces, lists, folders) based on business changes * Generate comprehensive task reports using filtering * Monitor team productivity through time tracking integration * Analyze project progress across different views **Team Collaboration Automation** * Update comments with automated progress reports * Manage checklist completion based on workflow milestones * Assign tasks and subtasks dynamically * Coordinate team access and permissions > πŸ’‘ **Best Practice**: Use ClickUp actions to seamlessly integrate project management into your business processes - from automated task creation and updates to comprehensive team coordination and productivity tracking across complex project hierarchies # Jira Jira integration in Lleverage enables you to automate issue tracking, project management, and team collaboration workflows directly with your Jira Cloud instance. Create, update, and manage issues, projects, and workflows while maintaining comprehensive project tracking and team coordination seamlessly within your automated processes. ### Key Features * **Issue management** - Create, update, transition, and track issues with comprehensive properties * **Advanced search** - Use JQL (Jira Query Language) for powerful issue filtering and retrieval * **Project operations** - Manage projects, versions, and project metadata * **Workflow automation** - Handle issue transitions and status changes * **Team collaboration** - Manage assignees, watchers, and comments * **Attachment handling** - Add single or multiple attachments to issues * **Custom fields** - Work with custom field options and contexts * **User management** - Retrieve user details and manage assignments * **Task tracking** - Monitor long-running operations and background tasks ### Key Jira Concepts **Understanding Jira Structure** * **Cloud ID**: Unique identifier for your Jira Cloud instance (appears in dropdowns after connection) * **Issue**: Individual work item, bug, task, or story within a project * **Project**: Container for related issues, with specific workflows and configurations * **Issue Type**: Category of issue (Bug, Task, Story, Epic, etc.) * **Transition**: Movement from one status to another in the workflow * **Status**: Current state of an issue (To Do, In Progress, Done, etc.) * **Workflow**: Sequence of statuses and transitions that issues follow * **Assignee**: User responsible for working on the issue * **Watcher**: User who receives notifications about issue changes * **JQL**: Jira Query Language for advanced searching and filtering **Project and Version Management** * **Project Version**: Release or milestone within a project * **Custom Field**: Additional data fields specific to your organization's needs * **Context**: Scope where custom fields are available (specific projects or issue types) * **Field Options**: Available values for custom select fields **Collaboration Features** * **Comments**: Discussion and updates on issues * **Attachments**: Files associated with issues * **History**: Record of all changes made to an issue * **Metadata**: Additional information about issues, projects, and users ### How to Add Jira Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Jira integration: * Select "External Apps" from the categories * Search for "Jira" in the provider list, or * Scroll down to find Jira in the alphabetical list 3. Click on Jira to view available actions 4. Select your desired Jira action from the comprehensive list ### How to Connect Your Jira Account **Initial Setup** 1. Click "Connect Jira Account" in any Jira action 2. Follow the Jira authentication process for your Cloud instance 3. Grant necessary permissions for issue and project access 4. Your **Cloud ID** will automatically populate in dropdown selections 5. User-specific dropdowns (Assignee ID, User ID) will be pre-filled with your account information > πŸ’‘ **Cloud ID**: This unique identifier for your Jira instance appears automatically after connection and is required for all Jira operations. ### How to Configure Jira Actions #### How to Search and Retrieve Issues **Search Issues with JQL** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Enter **JQL Query** using Jira Query Language syntax 4. Configure optional properties: * **Max Results**: Limit number of issues returned * **Fields**: Specify which issue fields to retrieve * **Expand**: Include additional data (comments, attachments, etc.) * **Properties**: Include issue properties * **Fields by Key**: Retrieve fields using their keys rather than names * **Validate Query**: Check JQL syntax before execution > πŸ’‘ **JQL Examples**: > > * `project = "PROJ" AND status = "In Progress"` > * `assignee = currentUser() AND created >= -7d` > * `labels = "urgent" OR priority = "High"` > πŸ’‘ **Use case**: Find issues matching complex criteria for batch operations, generate reports on specific issue sets, or retrieve issues for automated processing based on sophisticated filters. **Get Issue** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Issue ID or Key** from dropdown 4. Configure optional properties: * **Fields**: Specify which issue data to retrieve * **Fields by Key**: Use field keys instead of names * **Properties**: Include issue properties * **Update History**: Include change history * **Expand**: Include additional related data > πŸ’‘ **Use case**: Retrieve detailed information about specific issues for workflow decisions, get current issue status for processing, or extract issue data for integration with other systems. #### How to Manage Issues **Create Issue** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Project ID** from dropdown 4. Select **Issue Type** (Bug, Task, Story, etc.) 5. Configure optional properties: * **History**: Include creation history * **Metadata**: Add issue metadata * **Properties**: Set issue properties * **Update**: Specify additional fields during creation * **Additional Properties**: Set custom fields and advanced options > πŸ’‘ **Subtasks**: When subtask creation is enabled in your project, you can create subtasks under parent issues. > πŸ’‘ **Use case**: Automatically create issues from external triggers (support tickets, bug reports), generate tasks from workflow conditions, or establish work items with complete project context. **Update Issue** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Issue ID or Key** from dropdown 4. Configure optional properties: * **History**: Update change history * **Metadata**: Modify issue metadata * **Properties**: Update issue properties * **Additional Properties**: Modify custom fields * **Project ID**: Move issue to different project * **Notify Users**: Control notification settings * **Override Screen Security**: Bypass field restrictions * **Override Editable Flag**: Allow editing of restricted fields * **Transition ID**: Apply transition during update * **Transition Looped**: Handle transition loops > πŸ’‘ **Use case**: Update issue progress based on external system changes, modify issue details from workflow processing, or synchronize issue data with other tools. **Transition Issue** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Issue ID or Key** from dropdown 4. Select **Transition** to apply from dropdown 5. Configure optional properties: * **Fields**: Update fields during transition * **Update**: Additional field updates * **Issue Metadata**: Modify metadata during transition * **Properties**: Update properties * **Additional Properties**: Handle custom fields > πŸ’‘ **Use case**: Move issues through workflow stages automatically, update issue status based on external events, or trigger workflow progression from automated processes. **Assign Issue** 1. Connect your Jira account 2. Select **Account ID** (pre-filled after connection) 3. Choose **Issue ID or Key** from dropdown 4. Select **Assignee ID** from dropdown (pre-populated with available users) > πŸ’‘ **Use case**: Automatically assign issues based on expertise, workload, or workflow conditions, reassign issues when team roles change, or distribute work based on automated criteria. #### How to Manage Projects **Get All Projects** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Configure optional properties: * **Recent**: Show recently accessed projects * **Properties**: Include project properties * **Expand**: Include additional project data > πŸ’‘ **Use case**: Audit project structure, retrieve available projects for issue creation, or generate project reports and metadata. **Delete Project** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Project ID** from dropdown 4. Enable **Enable Undo** checkbox for recovery option > ⚠️ **Warning**: Project deletion is a significant operation. Ensure you have backups and proper authorization before deleting projects. > πŸ’‘ **Use case**: Clean up completed or obsolete projects, remove test projects, or manage project lifecycle as part of organizational workflows. **Create Version in Project** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Project** from dropdown 4. Enter **Version Name** for the new release 5. Configure optional properties: * **Description**: Version description and notes * **Archived**: Set archive status * **Released**: Mark as released version * **Start Date**: Version start date * **Release Date**: Planned or actual release date * **Move Unfixed Issues To**: Handle incomplete issues * **Expand**: Include additional version data > πŸ’‘ **Use case**: Automatically create release versions based on development milestones, manage version lifecycle through workflows, or coordinate release planning with project timelines. #### How to Handle Collaboration **Add Watcher to Issue** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Issue ID or Key** from dropdown 4. Select **User ID** from dropdown (pre-populated with available users) > πŸ’‘ **Use case**: Automatically add stakeholders as watchers based on issue type or content, notify team members of critical issues, or maintain visibility for specific user groups. **List Issue Comments** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Issue ID** from dropdown 4. Configure optional properties: * **Order By**: Sort comments by date or other criteria * **Expand**: Include additional comment data > πŸ’‘ **Use case**: Retrieve comment history for analysis, extract discussion context for workflow decisions, or monitor team communication on specific issues. #### How to Manage Attachments **Add Attachment to Issue** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Issue ID or Key** from dropdown 4. Enter **File Name** for the attachment > πŸ’‘ **Use case**: Automatically attach workflow outputs to issues, add generated reports to project issues, or include relevant files based on issue content. **Add Multiple Attachments to Issue** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Issue ID or Key** from dropdown 4. Select **File Names** from dropdown for batch attachment > πŸ’‘ **Use case**: Attach comprehensive documentation sets, add multiple files from workflow processing, or include related files in bulk operations. #### How to Work with Users and Advanced Features **Get Users** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Configure optional properties: * **Query**: Search for specific users * **Expand**: Include additional user data > πŸ’‘ **Use case**: Retrieve team member information for assignments, audit user access across projects, or populate user selection options in workflows. **Get User** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Assignee ID** from dropdown (pre-populated) 4. Configure optional properties: * **Expand**: Include detailed user information > πŸ’‘ **Use case**: Get specific user details for workflow decisions, retrieve user metadata for reporting, or validate user information for automated assignments. **Get Transitions** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Issue ID or Key** from dropdown 4. Configure optional properties: * **Transition ID**: Get specific transition details * **Skip Remote Only Conditions**: Include all transitions * **Include Unavailable Transitions**: Show restricted transitions * **Sort by Ops**: Order transitions by operations * **Status**: Filter by target status * **Expand**: Include additional transition data > πŸ’‘ **Use case**: Determine available workflow actions for issues, validate transition permissions before automation, or audit workflow configurations. **Get Task** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Enter **Task ID** for long-running operation monitoring > πŸ’‘ **Use case**: Monitor progress of bulk operations, track background task completion, or handle asynchronous Jira operations in workflows. **Create Custom Field Options Context** 1. Connect your Jira account 2. Select **Cloud ID** from dropdown 3. Choose **Field ID** from dropdown 4. Select **Context ID** from dropdown 5. Choose **Options** from dropdown > πŸ’‘ **Use case**: Manage custom field configurations programmatically, maintain field options across projects, or synchronize custom field data with external systems. ### Understanding JQL (Jira Query Language) **JQL Basics** JQL is Jira's powerful query language for searching issues: * **Field operators**: `=`, `!=`, `>`, `<`, `>=`, `<=` * **Text operators**: `~` (contains), `!~` (does not contain) * **List operators**: `IN`, `NOT IN` * **Logical operators**: `AND`, `OR`, `NOT` **Common JQL Functions** * `currentUser()`: Current logged-in user * `now()`: Current date/time * `startOfDay()`, `endOfDay()`: Time boundaries * `membersOf()`: Members of a group > πŸ’‘ **JQL Tips**: Start with simple queries and build complexity gradually. Use Jira's query builder to learn syntax before implementing in workflows. ### Important Considerations * Cloud ID uniquely identifies your Jira instance and is required for all operations * Issue keys are project-specific (e.g., PROJ-123) while Issue IDs are globally unique numbers * Transitions depend on workflow configuration and user permissions * Custom fields require proper context configuration for visibility * JQL queries can be complex but provide powerful filtering capabilities * Background tasks may require monitoring for completion * Project permissions affect available operations and data access > ⚠️ **Permissions**: Ensure your Jira account has appropriate permissions for the projects and operations your workflows need to perform. ### How Jira Actions Work in Your Workflow 1. Add the appropriate Jira action based on your issue tracking needs 2. Connect your Jira account securely (Cloud ID auto-populates) 3. Configure required fields (projects, issues, queries, etc.) 4. Set optional properties for advanced functionality and data retrieval 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the Jira action will execute the specified operation 7. Issue and project data become available as variables for subsequent workflow actions ### Common Workflow Patterns **Automated Issue Management** * Create issues from external triggers (support requests, monitoring alerts) * Update issue status based on development pipeline progress * Transition issues through workflow stages automatically * Assign issues based on expertise, workload, or project requirements **Advanced Issue Processing** * Use JQL to find issues matching complex criteria for batch operations * Retrieve issue data for reporting and analysis * Synchronize issue information with external project management tools * Monitor long-running operations through task tracking **Project and Release Management** * Create project versions based on development milestones * Manage project lifecycle through automated workflows * Coordinate release planning with version management * Archive completed projects and versions **Team Collaboration Automation** * Add watchers to issues based on content or priority * Attach workflow outputs and generated reports to issues * Monitor team communication through comment analysis * Manage user assignments across multiple projects > πŸ’‘ **Best Practice**: Use Jira actions to seamlessly integrate issue tracking into your development and project management processes - from automated issue creation and status updates to comprehensive project coordination and team collaboration across complex organizational workflows. # Linear Linear integration in Lleverage enables you to automate issue tracking and project management workflows directly with your Linear workspace. Create, update, and manage issues while maintaining team coordination and project progress tracking seamlessly within your automated processes. ### Key Features * **Issue management** - Create, update, and track issues with detailed properties * **Team coordination** - Manage team assignments and issue ownership * **Project organization** - Work with teams, projects, and issue states * **Advanced search** - Find issues using filters, labels, and status criteria * **Status tracking** - Monitor issue progress through workflow states * **Label system** - Organize and categorize issues with labels * **Archive handling** - Manage archived issues and historical data * **Flexible filtering** - Advanced filtering options for issue retrieval ### Key Linear Concepts **Understanding Linear Structure** * **Team**: Group of people working together, containing projects and issues * **Issue**: Individual work item, bug report, or task within a team * **Project**: Collection of related issues and milestones within a team * **State (Status)**: Current stage of an issue (Backlog, In Progress, Done, etc.) * **Assignee**: Team member responsible for working on and completing an issue * **Labels**: Tags used to categorize and organize issues by type, priority, or theme * **Archive**: Storage for completed or inactive issues to maintain workspace clarity **Issue Properties** * **Title**: Brief description of the issue or task * **Description**: Detailed explanation of the issue, requirements, or context * **Team**: Which team owns and is responsible for the issue * **State/Status**: Current progress stage of the issue * **Project**: Associated project or milestone grouping ### How to Add Linear Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Linear integration: * Select "External Apps" from the categories * Search for "Linear" in the provider list, or * Scroll down to find Linear in the alphabetical list 3. Click on Linear to view available actions 4. Select your desired Linear action from the available options ### How to Connect Your Linear Account **Initial Setup** 1. Click "Connect Linear Account" in any Linear action 2. Follow the Linear authentication process and sign in with your Linear account 3. Grant necessary permissions for team and issue access 4. Your connected account will be available across all Linear actions > πŸ’‘ The app to connect is labelled **Linear** and signs in with your Linear account (OAuth): you approve access on Linear's own sign-in screen rather than entering an API key. > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for the teams and projects your workflows need to access. ### How to Configure Linear Actions #### How to Manage Issues **Create Issue** 1. Connect your Linear account 2. Select **Team** from dropdown where the issue should be created 3. Enter **Title** for the new issue 4. Configure optional properties: * **Project**: Associate issue with specific project or milestone * **Description**: Add detailed context and requirements * **Assignee**: Assign responsibility to a team member * **State (Status)**: Set initial issue status * **Labels**: Add categorization tags > πŸ’‘ **Use case**: Automatically create issues from bug reports, generate tasks from form submissions, or establish work items from workflow triggers with complete context and team assignments. **Update Issue** 1. Connect your Linear account 2. Select **Team** from dropdown 3. Choose **Issue** to modify from dropdown 4. Configure optional properties: * **Title**: Change issue title * **Description**: Update issue details and context * **Team**: Move issue to different team * **State (Status)**: Update progress status * **Assignee**: Change issue ownership > πŸ’‘ **Use case**: Update issue progress based on external system changes, modify assignments when team roles change, or synchronize issue status with workflow completion. **Get Issue** 1. Connect your Linear account 2. Select **Issue** from dropdown to retrieve detailed information > πŸ’‘ **Use case**: Retrieve current issue details for workflow decisions, get issue status for reporting, or extract issue data for integration with other systems. #### How to Search and Find Issues **Search Issues** 1. Connect your Linear account 2. Select **Team** from dropdown to limit search scope 3. Configure optional properties for advanced filtering: * **Project**: Limit search to specific project * **Query**: Text search across issue titles and descriptions * **State (Status)**: Filter by current issue status * **Assignee**: Find issues assigned to specific team member * **Labels**: Filter by issue categorization tags * **Order By**: Sort results by specific criteria * **Include Archive**: Include archived issues in search results > πŸ’‘ **Use case**: Locate issues for automated updates, find work items matching specific criteria, or generate reports on issues meeting particular conditions. #### How to Manage Teams **Get Team** 1. Connect your Linear account 2. Retrieves information about teams accessible to your account > πŸ’‘ **Use case**: Audit team structure, retrieve available teams for issue assignment, or get team metadata for workflow decisions. ### Understanding Issue States and Workflow **State Management** Linear uses customizable workflow states to track issue progress: * **Backlog**: Issues waiting to be started * **In Progress**: Issues currently being worked on * **In Review**: Issues pending review or approval * **Done**: Completed issues * **Canceled**: Issues that won't be completed > πŸ’‘ **Custom States**: Teams can create custom states that match their specific workflow needs. **Status Tracking** * Issues move through states as work progresses * State changes can trigger workflow automations * Status provides visibility into team progress and bottlenecks ### Important Considerations * Teams are the primary organizational unit containing issues and projects * Issues belong to specific teams and can be moved between teams * States (Status) represent workflow progress and are customizable per team * Labels provide flexible categorization beyond team and project structure * Archive functionality helps maintain workspace clarity while preserving history * Search functionality supports both simple queries and advanced filtering * Projects group related issues but issues can exist without project association > ⚠️ **Team Selection**: Always select the appropriate team first, as this determines available issues, projects, and workflow states. ### How Linear Actions Work in Your Workflow 1. Add the appropriate Linear action based on your issue tracking needs 2. Connect your Linear account securely 3. Configure required fields (team, issue details, search criteria, etc.) 4. Set optional properties for advanced functionality and filtering 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the Linear action will execute the specified operation 7. Issue and team data become available as variables for subsequent workflow actions ### Common Workflow Patterns **Automated Issue Management** * Create issues automatically from external triggers (bug reports, feature requests) * Update issue status based on development pipeline progress * Assign issues to team members based on expertise or availability * Move issues between teams when ownership changes **Progress Tracking and Reporting** * Search for issues meeting specific criteria for progress reports * Monitor issue completion rates across teams and projects * Track issue assignment distribution and workload balance * Generate status updates based on issue state changes **Integration with Development Workflows** * Update issue status when code is deployed * Create issues from failed automated tests or monitoring alerts * Link issue progress to external project management systems * Synchronize issue data with other team collaboration tools **Team Coordination** * Automatically assign issues based on team member specialization * Update issue descriptions with additional context from workflows * Search and filter issues for team planning and sprint management * Archive completed issues to maintain workspace organization > πŸ’‘ **Best Practice**: Use Linear actions to seamlessly integrate issue tracking into your development and project management processes - from automated issue creation to progress tracking and team coordination across complex project workflows. # Hubspot HubSpot integration in Lleverage enables you to automate customer relationship management (CRM), marketing, and sales workflows directly with your HubSpot account. Manage contacts, companies, deals, tickets, and workflows while maintaining comprehensive customer data and sales pipeline tracking seamlessly within your automated processes. ### Key Features * **CRM management** - Handle contacts, companies, deals, and customer objects * **Sales pipeline** - Create and update deals, track sales progress * **Customer support** - Manage tickets and customer service workflows * **Marketing automation** - Enroll contacts in workflows and manage campaigns * **Meeting coordination** - Create meetings and manage associations * **Task management** - Create and track tasks across your organization * **Lead management** - Handle lead generation and qualification processes * **Engagement tracking** - Record customer interactions and touchpoints * **File management** - Generate public URLs for uploaded files * **Advanced search** - Find CRM objects using flexible search criteria ### Key HubSpot Concepts **Understanding HubSpot CRM Structure** * **Contact**: Individual person in your CRM with contact details and interaction history * **Company**: Organization or business entity that contacts may be associated with * **Deal**: Sales opportunity or potential transaction in your sales pipeline * **Ticket**: Customer service request or support issue requiring resolution * **Lead**: Potential customer who has shown interest but isn't yet qualified * **Task**: Action item or to-do associated with contacts, companies, or deals * **Meeting**: Scheduled interaction with contacts or prospects * **Engagement**: Record of interaction or communication with a contact * **Workflow**: Automated sequence of actions triggered by specific conditions * **Custom Object**: Organization-specific data objects beyond standard CRM entities **HubSpot Object Types** Available object types for search and management: * **Contacts**: Individual people and their information * **Companies**: Organizations and business entities * **Deals**: Sales opportunities and pipeline items * **Tickets**: Customer service and support requests * **Line Items**: Products or services within deals * **Products**: Items or services your organization offers * **Feedback Submissions**: Customer feedback and survey responses * **Leads**: Potential customers in early stages * **Custom Objects**: Organization-specific data structures **File and URL Management** * **Public URL**: Accessible link for files uploaded to HubSpot forms * **URL Expiration**: Time limit for public file access (default: 3,600 seconds/1 hour) * **File Associations**: Links between files and CRM objects ### How to Add HubSpot Integration 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to HubSpot integration: * Select "External Apps" from the categories * Search for "HubSpot" in the provider list, or * Scroll down to find HubSpot in the alphabetical list 3. Click on HubSpot to view available actions 4. Select your desired HubSpot action from the comprehensive list ### How to Connect Your HubSpot Account **Initial Setup** 1. Click "Connect HubSpot Account" in any HubSpot action 2. Follow the HubSpot authentication process 3. Grant necessary permissions for CRM, sales, and marketing access 4. Your connected account will be available across all HubSpot actions > πŸ’‘ **Permissions**: Ensure you grant appropriate permissions for the HubSpot features and data your workflows need to access. ### How to Configure HubSpot Actions #### How to Search and Retrieve Data **Search CRM Objects** 1. Connect your HubSpot account 2. Select **Object Type** from dropdown: * Contacts, Companies, Deals, Tickets, Line Items, Products * Feedback Submissions, Leads, Custom Objects 3. Configure optional properties: * **Create if Not Found**: Automatically create object if search returns no results (checkbox) > πŸ’‘ **Use case**: Locate CRM records for automated updates, find objects matching specific criteria, or ensure data exists before processing workflows. **Get Contact** 1. Connect your HubSpot account 2. Select **Contact ID** from dropdown 3. Configure optional properties: * **Additional Properties to Retrieve**: Specify which contact fields to include > πŸ’‘ **Use case**: Retrieve detailed contact information for personalization, get contact data for workflow decisions, or extract contact details for integration with other systems. **Get Company** 1. Connect your HubSpot account 2. Select **Company ID** from dropdown 3. Configure optional properties: * **Additional Properties to Retrieve**: Specify which company fields to include > πŸ’‘ **Use case**: Get company details for account-based workflows, retrieve organization information for reporting, or extract company data for sales processes. **Get Deal** 1. Connect your HubSpot account 2. Select **Deal ID** from dropdown 3. Configure optional properties: * **Additional Properties to Retrieve**: Specify which deal fields to include > πŸ’‘ **Use case**: Retrieve sales opportunity details for pipeline reporting, get deal information for workflow decisions, or extract deal data for sales automation. #### How to Manage Meetings and Engagements **Get Meeting** 1. Connect your HubSpot account 2. Select **Meeting ID** from dropdown 3. Configure optional properties: * **Additional Properties to Retrieve**: Specify which meeting fields to include > πŸ’‘ **Use case**: Retrieve meeting details for follow-up automation, get meeting information for reporting, or extract meeting data for calendar integration. **Get Associated Meetings** 1. Connect your HubSpot account 2. Enter **From** input (starting point for search) 3. Select **From Object Type** from dropdown 4. Choose **Object ID** from dropdown 5. Configure optional properties: * **Time Frame**: Limit meetings to specific time period * **Most Recent Only**: Return only the latest meetings * **Additional Properties**: Include specific meeting data > πŸ’‘ **Use case**: Find meetings related to specific contacts or deals, retrieve meeting history for relationship analysis, or get associated meetings for workflow processing. **Create Meeting** 1. Connect your HubSpot account 2. Configure meeting details and properties 3. Set optional associations to other CRM objects (contacts, companies, deals) > πŸ’‘ **Use case**: Automatically schedule meetings from workflow triggers, create follow-up meetings based on deal progress, or establish meetings with new qualified leads. **Create Engagement** 1. Connect your HubSpot account 2. Create interaction records for contacts 3. Track communication and touchpoints > πŸ’‘ **Use case**: Log automated communications with contacts, record workflow-generated interactions, or track engagement from external systems. #### How to Manage Sales Pipeline **Create Deal** 1. Connect your HubSpot account 2. Set up new sales opportunities with complete deal properties 3. Associate with relevant contacts and companies > πŸ’‘ **Use case**: Automatically create deals from qualified leads, generate sales opportunities from form submissions, or establish deals based on customer behavior triggers. **Update Deal** 1. Connect your HubSpot account 2. Modify existing deal properties and status 3. Update pipeline stage and deal values > πŸ’‘ **Use case**: Update deal progress based on customer actions, modify deal values from external data, or synchronize deal status with other sales tools. #### How to Handle Customer Support **Create Ticket** 1. Connect your HubSpot account 2. Generate customer service requests with complete ticket properties 3. Associate with relevant contacts and companies > πŸ’‘ **Use case**: Automatically create support tickets from form submissions, generate tickets from monitoring alerts, or establish customer service requests from workflow triggers. **Update Ticket** 1. Connect your HubSpot account 2. Modify ticket status, priority, and resolution details 3. Track customer service progress > πŸ’‘ **Use case**: Update ticket status based on resolution progress, modify ticket priority from external systems, or synchronize support data across platforms. #### How to Manage Contacts and Leads **Create Contact** 1. Connect your HubSpot account 2. Add new contacts with comprehensive contact properties 3. Set initial engagement and lifecycle stage > πŸ’‘ **Use case**: Add contacts from form submissions, create contacts from external lead sources, or establish contact records from workflow data. **Update Contact** 1. Connect your HubSpot account 2. Modify contact properties, lifecycle stage, and engagement data 3. Update contact information from external sources > πŸ’‘ **Use case**: Keep contact information current from external systems, update contact engagement based on behavior, or synchronize contact data across platforms. **Create Lead** 1. Connect your HubSpot account 2. Generate new leads with qualification data 3. Set lead source and initial properties > πŸ’‘ **Use case**: Create leads from marketing campaigns, generate leads from website behavior, or establish lead records from external sources. **Update Lead** 1. Connect your HubSpot account 2. Modify lead qualification status and properties 3. Progress leads through qualification stages > πŸ’‘ **Use case**: Update lead scores based on behavior, modify lead status from qualification workflows, or synchronize lead data with marketing tools. #### How to Manage Workflows and Automation **Enroll Contact into Workflow** 1. Connect your HubSpot account 2. Select **Workflow** from dropdown 3. Choose **Contact Email** from dropdown to identify the contact 4. Automatically add contacts to HubSpot marketing or sales workflows > πŸ’‘ **Note**: The workflow API currently only supports contact enrollment. > πŸ’‘ **Use case**: Trigger marketing sequences based on customer behavior, enroll contacts in nurture campaigns from external events, or start onboarding workflows for new customers. #### How to Handle Files and URLs **Get File Public URL** 1. Connect your HubSpot account 2. Select **File URL** from dropdown 3. Configure optional properties: * **Public URL Expiration**: Set access time limit (default: 3,600 seconds/1 hour) > πŸ’‘ **Use case**: Generate accessible links for files uploaded through HubSpot forms, create temporary access to customer documents, or provide file access for external integrations. #### How to Manage Tasks and Activities **Create Task** 1. Connect your HubSpot account 2. Generate action items with complete task properties 3. Associate with relevant contacts, companies, or deals > πŸ’‘ **Use case**: Create follow-up tasks from customer interactions, generate action items from deal progress, or establish tasks based on workflow milestones. **Update Task** 1. Connect your HubSpot account 2. Modify task status, priority, and completion details 3. Update task assignments and due dates > πŸ’‘ **Use case**: Update task progress from external systems, modify task priorities based on customer needs, or synchronize task management across platforms. #### How to Manage Custom Objects **Update Customer Object** 1. Connect your HubSpot account 2. Modify custom object properties specific to your organization 3. Update relationships with standard CRM objects > πŸ’‘ **Use case**: Maintain custom data structures, update organization-specific information, or synchronize custom object data with external systems. ### Understanding HubSpot Object Relationships **CRM Object Associations** * **Contacts** can be associated with Companies, Deals, and Tickets * **Companies** can have multiple Contacts and Deals * **Deals** can be associated with Contacts and Companies * **Tickets** can be linked to Contacts and Companies * **Meetings** can be associated with any CRM object * **Tasks** can be related to Contacts, Companies, or Deals **Workflow Integration** * Workflows automate sequences of actions based on triggers * Contact enrollment triggers marketing and sales sequences * Workflow actions can update properties, send emails, create tasks * Integration enables external triggers for HubSpot workflows ### Important Considerations * Object IDs are unique identifiers required for specific record operations * Additional Properties allow you to specify which data fields to retrieve or update * Create if Not Found option automatically generates records when searches return no results * Public URL expiration defaults to 1 hour (3,600 seconds) for security * Workflow enrollment currently supports contacts only * Custom objects require proper setup in your HubSpot account * File URLs must be from files uploaded through HubSpot forms > ⚠️ **Data Management**: Be cautious with "Create if Not Found" options to avoid duplicate records. Ensure proper data validation before automatic record creation. ### How HubSpot Actions Work in Your Workflow 1. Add the appropriate HubSpot action based on your CRM and marketing needs 2. Connect your HubSpot account securely 3. Configure required fields (object types, IDs, search criteria, etc.) 4. Set optional properties for additional data retrieval and advanced functionality 5. Connect the action to other workflow steps as needed 6. When the workflow runs, the HubSpot action will execute the specified operation 7. CRM and customer data become available as variables for subsequent workflow actions ### Common Workflow Patterns **Lead Management and Qualification** * Create leads from form submissions and external sources * Search for existing contacts before creating duplicates * Enroll qualified leads into nurture workflows * Update lead scores based on engagement behavior **Sales Pipeline Automation** * Create deals from qualified opportunities * Update deal stages based on customer actions * Associate deals with relevant contacts and companies * Generate follow-up tasks for sales team **Customer Support Integration** * Create tickets from support requests and monitoring alerts * Update ticket status based on resolution progress * Associate tickets with customer contact and company records * Generate tasks for support team follow-up **Marketing Campaign Coordination** * Enroll contacts in workflows based on behavior triggers * Update contact properties from campaign engagement * Create engagements to track marketing touchpoints * Generate public URLs for campaign assets **Data Synchronization and Reporting** * Search CRM objects for reporting and analysis * Update contact and company information from external sources * Retrieve associated meetings and activities for relationship analysis * Maintain custom objects with organization-specific data > πŸ’‘ **Best Practice**: Use HubSpot actions to seamlessly integrate customer relationship management into your business processes - from automated lead qualification and deal progression to comprehensive customer support and marketing campaign coordination across your entire customer lifecycle. # Zoho CRM Zoho CRM integration in Lleverage connects your workflows and agents to your CRM, so they can create and update records, keep customer data current, and react automatically when records change in Zoho. ### How to Connect 1. **Go to Settings > Connections** in your project 2. **Pick Zoho CRM** from the list of apps 3. **Choose which actions** the connection should allow and who should have access (shared or personal) 4. **Choose "Connect Now"** and sign in with your Zoho account, or send an authentication link so a colleague can connect on your behalf > πŸ’‘ Zoho CRM signs in with your Zoho account (OAuth): you approve access on Zoho's own sign-in screen rather than entering an API key. ### What Zoho CRM Can Do * **Records** - create, update, upsert, retrieve, find, query, delete and merge records in any module (leads, contacts, deals and so on) * **Related records** - retrieve and update records related to another record * **Notes and tags** - add notes to records, and add or remove tags * **Attachments** - upload and download record attachments * **Ownership and leads** - change a record's owner and convert leads * **Automation** - enrol a record in a cadence and move a record through a blueprint stage ### Triggers Zoho CRM provides three triggers, so workflows can start automatically when: * **A record is created** * **A record is updated** * **A record is deleted** Zoho notifies Lleverage when these events happen, so workflows start straight away. > πŸ’‘ **Use case**: Enrich new leads the moment they are created, keep other systems in sync when records change, or alert the team when key records are deleted. ### Important Considerations * The connected account's role and permissions in Zoho CRM determine what the integration can see and change * Record actions ask you to pick the module first, so the fields match your CRM's setup # Zendesk Zendesk integration in Lleverage connects your workflows and agents to your support desk, so they can create and update tickets, manage users and organisations, and react automatically as tickets move through your queue. ### How to Connect 1. **Go to Settings > Connections** in your project 2. **Pick Zendesk** from the list of apps 3. **Enter your Zendesk subdomain** - the first part of your Zendesk web address, e.g. "yourcompany" if you sign in at yourcompany.zendesk.com 4. **Choose which actions** the connection should allow and who should have access (shared or personal) 5. **Choose "Connect Now"** and sign in with your Zendesk account > πŸ’‘ Zendesk signs in with your Zendesk account (OAuth) once you've provided the subdomain, so there's no API key to manage. ### What Zendesk Can Do * **Tickets** - create, update, retrieve, list and search tickets * **Ticket comments** - add comments to tickets and list a ticket's existing comments * **Users** - create, update, retrieve, list and search users * **Organisations** - create, update, retrieve, list and search organisations ### Triggers Zendesk provides four triggers, so workflows can start automatically when: * **A new ticket** is created * **A new comment** is added to a ticket * **A ticket's status changes** * **A ticket is assigned** Zendesk notifies Lleverage when these events happen, so workflows start straight away. > πŸ’‘ **Use case**: Triage and categorise new tickets automatically, draft first responses for agents to approve, or escalate tickets the moment they change status. ### Important Considerations * The connected account's role in Zendesk determines what the integration can see and change * Search actions use Zendesk's own search syntax, so anything you can search for in Zendesk you can search for here # Typeform Typeform integration in Lleverage connects your workflows and agents to your forms, so submissions can flow straight into automated processes the moment they arrive. ### How to Connect 1. **Go to Settings > Connections** in your project 2. **Pick Typeform** from the list of apps 3. **Choose which actions** the connection should allow and who should have access (shared or personal) 4. **Choose "Connect Now"** and sign in with your Typeform account, or send an authentication link so a colleague can connect on your behalf > πŸ’‘ Typeform signs in with your Typeform account (OAuth), so there's no API key to manage. ### What Typeform Can Do * **Forms and workspaces** - list your workspaces and forms, and retrieve a form's details * **Responses** - fetch form responses for processing, and delete responses when they're no longer needed * **Webhooks** - create, inspect and remove the webhooks that deliver responses to other systems ### Triggers Typeform provides one trigger: **a form response is submitted**. Typeform notifies Lleverage the moment someone completes your form, so the workflow starts straight away with the submission's answers available as variables. > πŸ’‘ **Use case**: Route new sign-ups into your CRM, send a tailored follow-up email based on someone's answers, or start an approval process from an internal request form. ### Important Considerations * The connection works with forms the signed-in Typeform account can access * Deleting responses is permanent, so use it carefully in automated flows # Google BigQuery Google BigQuery integration in Lleverage connects your workflows and agents to your data warehouse, so they can look up datasets and run queries, bringing analytics data into your automated processes. ### How to Connect 1. **Go to Settings > Connections** in your project 2. **Pick Google BigQuery** from the list of apps 3. **Choose which actions** the connection should allow and who should have access (shared or personal) 4. **Choose "Connect Now"** and sign in with Google, or send an authentication link so a colleague can connect on your behalf ### What Google BigQuery Can Do * **Browsing** - list the datasets in your project and the tables within a dataset * **Querying** - run a query and use the results in the rest of your workflow > πŸ’‘ **Use case**: Pull the latest figures into a scheduled report, let an agent answer data questions with a live query, or check a metric before a workflow decides what to do next. ### Important Considerations * The signed-in Google account's access in BigQuery determines which datasets and tables are available * Queries run against your BigQuery project and count towards its usage, so keep scheduled queries efficient # Microsoft Dynamics 365 Business Central Microsoft Dynamics 365 Business Central integration in Lleverage connects your workflows and agents to your ERP, so they can look up customers and items, raise sales and purchase documents, and keep Business Central in step with the rest of your processes. ### How to Connect Business Central is an ERP connection, and ERP connections are set up together with the Lleverage team because they need configuration specific to your environment. 1. **Contact the Lleverage team** via support or your account manager to start the managed setup 2. **Sign in with Microsoft** using an account that has access to your Business Central environment when asked 3. **Confirm the connection** appears in Settings > Connections, ready for use in workflows and by agents > πŸ’‘ Once connected, you can control which actions the connection allows and which need approval before running, just like any other connection. ### What Business Central Can Do * **Customers** - create, update, find and list customers * **Vendors** - find and list vendors and retrieve their details * **Items** - find and list items and retrieve item details * **Sales orders** - create sales orders, add order lines, update and look up existing orders * **Sales invoices** - create invoices and invoice lines, and find or list existing invoices * **Sales quotes** - create and look up sales quotes * **Purchase invoices** - create invoices and invoice lines, update them, and find or list existing ones * **Companies and attachments** - list the companies in your environment, upload attachments, and batch several requests together > πŸ’‘ **Use case**: Turn an incoming order email into a sales order automatically, or let an agent look up a customer's open invoices before answering a query. ### Important Considerations * The connected account's permissions in Business Central determine what the integration can see and change * Most actions ask you to pick the company first, since Business Central environments often contain several # Microsoft Dynamics 365 Finance & Operations Microsoft Dynamics 365 Finance & Operations integration in Lleverage connects your workflows and agents to your ERP, so they can work with customers, vendors, products and sales and purchase documents without leaving your automated processes. ### How to Connect Finance & Operations is an ERP connection, and ERP connections are set up together with the Lleverage team because they need configuration specific to your environment. 1. **Contact the Lleverage team** via support or your account manager to start the managed setup 2. **Sign in with Microsoft** using an account that has access to your Finance & Operations environment when asked 3. **Confirm the connection** appears in Settings > Connections, ready for use in workflows and by agents > πŸ’‘ Once connected, you can control which actions the connection allows and which need approval before running, just like any other connection. ### What Finance & Operations Can Do * **Customers** - create, find and list customers and retrieve their details * **Vendors** - find and list vendors and retrieve their details * **Released products** - find and list released products and retrieve product details * **Sales orders** - create sales orders, add order lines, update and look up existing orders * **Sales quotations** - create and look up sales quotations * **Sales invoices** - find and list invoices and retrieve invoice details * **Purchase orders** - create and look up purchase orders * **Companies and batches** - list the companies in your environment and batch several requests together > πŸ’‘ **Use case**: Create sales orders automatically from incoming documents, or let an agent check product availability and existing orders before confirming with a customer. ### Important Considerations * The connected account's permissions in Finance & Operations determine what the integration can see and change * Most actions ask you to pick the company first, since environments often contain several legal entities # Dynamics NAV Dynamics NAV integration in Lleverage connects your workflows and agents to on-premise Microsoft Dynamics NAV (Navision), so long-standing ERP systems can take part in modern automated processes. ### How to Connect Dynamics NAV is an ERP connection, and ERP connections are set up together with the Lleverage team because they need configuration specific to your environment. 1. **Contact the Lleverage team** via support or your account manager to start the managed setup 2. **Provide the sign-in details** for your NAV environment: the connection authenticates with a username and password 3. **Confirm the connection** appears in Settings > Connections, ready for use in workflows and by agents > πŸ’‘ Once connected, you can control which actions the connection allows and which need approval before running, just like any other connection. ### What Dynamics NAV Can Do * **Customers** - create customers, look up individual customers and list them * **Vendors** - look up and list vendors * **Items** - look up and list items * **Sales orders** - create sales orders and look up or list existing ones * **Sales invoices** - look up and list sales invoices * **Companies** - list the companies in your environment > πŸ’‘ **Use case**: Feed orders captured by a workflow straight into NAV, or let an agent answer questions about customers and invoices held in your ERP. ### Important Considerations * The account used to connect determines what the integration can see and change in NAV * Most actions ask you to pick the company first # SAP S/4HANA SAP S/4HANA integration in Lleverage connects your workflows and agents to your SAP system, so they can work with business partners, products, sales and purchase documents, and react automatically when new documents are created in SAP. ### How to Connect SAP S/4HANA is an ERP connection, and ERP connections are set up together with the Lleverage team because they need configuration specific to your environment. 1. **Contact the Lleverage team** via support or your account manager to start the managed setup 2. **Provide the sign-in details** for your SAP system: cloud systems sign in with your SAP account, while on-premise systems can use a username and password or an API key 3. **Confirm the connection** appears in Settings > Connections, ready for use in workflows and by agents > πŸ’‘ Once connected, you can control which actions the connection allows and which need approval before running, just like any other connection. ### What SAP S/4HANA Can Do * **Business partners** - look up and list business partners * **Customers** - create, look up and list customers * **Suppliers** - look up and list suppliers * **Products** - create, look up and list products * **Sales orders** - create, look up and list sales orders * **Sales quotations** - create, look up and list sales quotations * **Purchase orders** - create, look up and list purchase orders * **Billing documents** - look up and list billing documents * **Company codes** - list the company codes in your system ### Triggers SAP S/4HANA provides six triggers, so workflows can start automatically when SAP records these events: * **A new sales order** is created * **A new purchase order** is created * **A new sales quotation** is created * **A new billing document** is created * **A new customer** is created * **A new supplier** is created > πŸ’‘ **Use case**: Start an approval workflow whenever a large purchase order is created, or notify the account team the moment a new customer appears in SAP. ### Important Considerations * The account used to connect determines what the integration can see and change in SAP * Triggers check SAP for new documents on a schedule, so there can be a short delay before the workflow starts # Keyboard Shortcuts Speed up your workflow building with keyboard shortcuts for common actions. Press βŒ˜β‡§ / (Mac) or Ctrl⇧ / (Windows) anywhere on the canvas to open the full shortcuts glossary. ### Application Shortcuts These shortcuts work within the Lleverage platform to help you build and manage workflows more efficiently. #### General | Action | Mac | Windows | | ------------------------- | ---- | ---------- | | Global Search | ⌘βŒ₯ K | Ctrl Alt K | | Export Workflow | ⌘βŒ₯ E | Ctrl Alt E | | Import Workflow | ⌘βŒ₯ O | Ctrl Alt O | | Publish Workflow | ⌘βŒ₯ P | Ctrl Alt P | | Publish Panel | ⌘βŒ₯ Y | Ctrl Alt Y | | Toggle Run Panel | ⌘βŒ₯ R | Ctrl Alt R | | Tests | ⌘βŒ₯ T | Ctrl Alt T | | Feedback | ⌘βŒ₯ G | Ctrl Alt G | | Open Documentation | βŒ˜β‡§ D | Ctrl⇧ D | | Keyboard Shortcuts (Help) | βŒ˜β‡§ / | Ctrl⇧ / | > πŸ’‘ Tests and Feedback open the run panel straight on the relevant tab. #### Canvas and Navigation | Action | Mac | Windows | | -------------------- | ------ | ------------ | | Run Workflow Now | βŒ˜β‡§ ↡ | Ctrl⇧ ↡ | | Add Action | βŒ˜β‡§ A | Ctrl⇧ A | | Find in Workflow | βŒ˜β‡§ F | Ctrl⇧ F | | Fit View | ⌘ 0 | Ctrl 0 | | Zoom In | ⌘ = | Ctrl = | | Zoom Out | ⌘ - | Ctrl - | | Centre Selected Node | βŒ˜β‡§ 1 | Ctrl⇧ 1 | | Toggle All Nodes | ⌘βŒ₯⇧ \[ | Ctrl Alt⇧ \[ | | Presentation Mode | βŒ˜β‡§ P | Ctrl⇧ P | > πŸ’‘ Presentation Mode hides all canvas controls for a clean view, which is handy when demoing a workflow. #### Editing | Action | Mac | Windows | | -------------- | ------ | ------- | | Select All | ⌘ A | Ctrl A | | Copy | ⌘ C | Ctrl C | | Paste | ⌘ V | Ctrl V | | Duplicate Node | ⌘ D | Ctrl D | | Delete Node | Delete | Delete | | Undo | ⌘ Z | Ctrl Z | | Redo | βŒ˜β‡§ Z | Ctrl⇧ Z | ### Browser Shortcuts (Protected) These are standard browser shortcuts that remain unchanged and cannot be overridden by the Lleverage platform. #### Navigation | Action | Mac | Windows | | ------------------ | ---- | ------- | | Back navigation | ⌘ ← | Alt ← | | Forward navigation | ⌘ β†’ | Alt β†’ | | Reload page | ⌘ R | Ctrl R | | Hard reload | βŒ˜β‡§ R | Ctrl F5 | #### Tab Management | Action | Mac | Windows | | ----------------- | ---- | ------- | | New tab | ⌘ T | Ctrl T | | Close tab | ⌘ W | Ctrl W | | Reopen closed tab | βŒ˜β‡§ T | Ctrl⇧ T | #### Browser Tools | Action | Mac | Windows | | ------------ | ---- | ------- | | Find on page | ⌘ F | Ctrl F | | Address bar | ⌘ L | Ctrl L | | Print | ⌘ P | Ctrl P | | Fullscreen | βŒƒβŒ˜ F | F11 | | History | ⌘ Y | Ctrl H | ### System Shortcuts (Protected) These are operating system shortcuts that function normally within your browser. | Action | Mac | Windows | | ---------------- | -------- | --------- | | Spotlight search | ⌘ Space | - | | App switcher | ⌘ Tab | Alt Tab | | Force quit | ⌘βŒ₯ Esc | Ctrl⇧ Esc | | Quit app | ⌘ Q | Alt F4 | | Minimise | ⌘ M | Win ↓ | | Emoji picker | βŒƒβŒ˜ Space | Win . | | Cut | ⌘ X | Ctrl X | > ⚠️ **Important**: Browser and system shortcuts are protected and cannot be overridden. They will always perform their standard functions even while using Lleverage. **Key Features:** * Application shortcuts for faster workflow building * Quick access to all major functions without using the mouse * Protected browser and system shortcuts maintain normal functionality * Help panel available anytime with βŒ˜β‡§ / (Mac) or Ctrl⇧ / (Windows) # Canvas Controls Canvas Controls in Lleverage provide tools to navigate, organize, and manage your workflow interface efficiently. These controls help you build and refine automations within the visual canvas environment. ### Key Features * **Navigation tools** for moving around the canvas * **Zoom controls** for adjusting your view * **Organization options** for arranging your actions * **Collapse/expand functions** for better workspace management * **Co-Pilot access** for AI-assisted workflow creation ### Understanding the Canvas Environment 1. The canvas is identified by the light gray background with a dotted pixel grid 2. Canvas controls are only available within the Canvas Studio 3. The canvas is where you place and connect your workflow actions 4. Your current view position determines where new actions appear when added > πŸ’‘ Think of the canvas as your workflow design space where all your automation building happens. ### How to Use Canvas Controls

Left side of Canvas

#### How to Add Actions to the Canvas 1. Click the "Add Action" button in the top left corner 2. Select an action from the menu 3. The action will appear in your current viewport, unconnected to other actions > πŸ’‘ This is just one way to add actions. You can also add them by clicking connection points on existing actions. #### How to Navigate the Canvas 1. Press and hold to move around the canvas 2. Use the zoom controls in the bottom left corner: * Minus (-) button: Zoom out * Plus (+) button: Zoom in * Percentage display: Shows current zoom level * Clicking percentage: Returns to 100% zoom > ⚠️ If you zoom out to 50% or less, actions will automatically collapse to conserve space since they become unreadable at smaller sizes.

Example interaction to reduce zoom levels

#### How to Adjust Your View 1. Zoom levels range from approximately 50% (minimum) to 100% (maximum) 2. Click the "fit to screen" button (four corners icon) to automatically adjust the view to show all actions 3. This feature ensures your entire workflow is visible at once when possible > πŸ’‘ The fit to screen function is particularly useful for getting an overview of complex workflows.

Fit to screen

#### How to Organize Your Canvas 1. Use the "reorganize" button (line/square/line icon) to automatically align actions 2. This creates consistent spacing between actions and aligns them in a logical flow 3. The system will position actions to maximize readability and connection clarity

Reorganise action cards

#### How to Collapse/Expand Actions 1. Use the arrow buttons to manage action display: * Arrow down: Collapses all actions to show only headers * Arrow up: Expands all actions to show full details 2. The arrow direction changes to indicate the current state 3. This helps manage complex workflows by reducing visual clutter > πŸ’‘ Collapsing actions is particularly useful when working with large workflows to get a better overview.

Expand and close action cards

#### How to Access Co-Pilot 1. Click the "Co-Pilot" text in the bottom left area 2. This activates or deactivates the Co-Pilot feature 3. When active, Co-Pilot can help generate and suggest workflow improvements > πŸ’‘ For more information about Co-Pilot functionality, visit the Co-Pilot section of the documentation.

Activate Co-Pilot

#### How to Get Support 1. Look for the chat icon in the bottom right corner (round circle with text icon) 2. This appears when a Lleverage agent is online 3. Click to open a live chat with support staff for immediate assistance > πŸ’‘ The support chat provides direct access to help from Lleverage staff when building your workflows.

Online chat to a Lleverage Agent

#### **How to Multi-Select and Manage Actions** 1. Click on an action to select it 2. Hold Shift and click additional actions to multi-select 3. Once selected, move all actions together by dragging 4. Look for the selection controls next to the "Add Action" button - this shows an icon and count of selected items 5. Use the available options for your selection: * **Create Workflow**: Convert selected actions into a subworkflow * **Duplicate**: Create copies of the selected actions * **Delete**: Remove the selected actions from your canvas > πŸ’‘ Multi-selection is particularly useful for organizing related actions or creating reusable workflow components. #### **How to Use the Mini Map** 1. Ensure no actions are currently selected on your canvas 2. Look for the mini map that appears when you have context outside your current window view 3. Use the mini map to navigate to different areas of your workflow 4. This provides a bird's-eye view of your entire canvas layout > πŸ’‘ The mini map helps you navigate large, complex workflows by showing the overall structure and your current viewport position. ### Important Canvas Control Considerations 1. The top right area is reserved for panels that provide additional workflow functionality 2. New actions are always added to your current view position 3. Automatic organization respects the connections between actions 4. Canvas controls are designed to help manage workflows of any complexity 5. The support chat is only available when agents are online > ⚠️ Always save your work before making major canvas reorganizations, although the system does maintain automatic version history. # Flow Control Flow Controls in Lleverage enable you to create sophisticated workflow logic with conditional branching, loops, and decision-making capabilities. These powerful tools allow you to build dynamic workflows that adapt to different conditions, process lists of data, and handle complex business logic seamlessly. ### Flow Control Types **Branch**: Creates conditional logic with If/ElseIf/Else paths that route workflow execution based on specific conditions

Branch Action

**Loop**: Processes each item in a list or array individually through a repeatable workflow sequence

Loop Action

**Get First Available Value**: Returns the first non-empty value from a list of options, providing fallback functionality

Get First Available Value Action

**Repeat**: Executes the same actions a specified number of times with counting capability

Repeat Action

**Do While**: Runs a sub-canvas repeatedly until it returns a result, for loops where you don't know the number of iterations up front **Continue**: Used inside a Do While loop to move on to the next iteration, optionally passing a value along **Return**: Ends the workflow with a result. The value it returns becomes the API response in API workflows, or the result handed back to the parent workflow in subworkflows **Set Session Title**: Gives the current workflow session a custom title so runs are easy to identify later **Track Metric**: Records one or more custom metric values during a run for analytics and monitoring > πŸ’‘ Flow controls create sub-canvases for their internal logic and can be nested within each other for complex workflow scenarios. ### How to Add Flow Controls 1. Open the Add Action menu using one of three methods: * Click the "Add Action" button in the top left corner * Click on a connection circle on an existing action card * Click and drag from one action to create a connection 2. Navigate to Flow Controls: * Select "All" or "Tools" from the categories * Scroll down to find the "Controls" subcategory at the bottom of the panel 3. Select your desired flow control 4. Configure the specific settings for your selected flow control type ### How to Configure Flow Controls #### How to Configure a Branch 1. Select "Branch" as your flow control type 2. Configure the **If** condition: * Set condition criteria using variables and operators * Examples: `variable equals "value"`, `number > 10`, `text contains "keyword"` 3. Add **ElseIf** conditions as needed: * Click to add additional conditional paths * Each ElseIf can have unique condition criteria * Conditions are evaluated in order from top to bottom 4. Configure **Else** condition for default behavior when no conditions match 5. Connect each condition path: * Drag from connection points on the right side of each condition * Link to different workflow actions based on your logic needs > ⚠️ Branch conditions are evaluated in order - the first matching condition determines the workflow path. **Branch Configuration Example**: ``` If: customer_tier equals "Premium" β†’ Connect to: Premium support workflow ElseIf: order_value > 1000 β†’ Connect to: Bulk discount workflow Else: (default case) β†’ Connect to: Standard processing ``` #### How to Configure a Loop 1. Select "Loop" as your flow control type 2. Configure the **Items** field: * Select a variable containing a list or array to process * Examples: `contact_list`, `uploaded_files`, `database_records` * Can use data from previous workflow actions or external sources 3. Click **Edit Loop** button to open the sub-canvas 4. Build the workflow for processing individual items: * Add actions that work with each list item * Use the loop item variable in your actions * Connect actions in the desired processing sequence 5. Return to main canvas using breadcrumb navigation > πŸ’‘ The loop processes each item individually and sequentially until all items are complete. **Loop Processing Flow**: 1. Takes first item from the list 2. Executes all sub-canvas actions with that item 3. Moves to next item and repeats 4. Continues until all items are processed 5. Workflow continues after loop completion #### How to Configure a Repeat 1. Select "Repeat" as your flow control type 2. Configure the **Repetitions** field: * Enter a specific number (e.g., 3, 10, 100) * Use a variable containing a number * Can be calculated from previous workflow actions 3. Click **Edit Repeat** button to open the sub-canvas 4. Build the workflow to repeat: * Add actions to perform multiple times * Actions execute identically each repetition * Current repetition number available as variable 5. Return to main canvas using breadcrumb navigation > πŸ’‘ Repeat is ideal for retry logic, periodic checks, or generating multiple similar outputs. **Repeat Example**: ``` Repetitions: 5 Sub-canvas contains: β†’ API health check β†’ Log results β†’ Wait 30 seconds Result: Performs health check 5 times with 30-second intervals ``` #### How to Configure Get First Available Value 1. Select "Get First Available Value" as your flow control type 2. Configure the **Inputs** section: * Add multiple variables or values to check * Order matters - values are evaluated from top to bottom * First non-empty value will be returned 3. Specify the **Values** to evaluate: * Can include variables, direct values, or expressions * Mix different data types as needed **Value Evaluation Process**: 1. Checks first input - returns value if not empty 2. If empty, moves to second input 3. Continues through all inputs sequentially 4. Returns first available (non-empty) value found 5. Returns null/empty if all inputs are empty **Get First Available Value Example**: ``` Inputs (evaluated in order): 1. user_mobile_phone 2. user_work_phone 3. user_home_phone 4. "555-0000" (default) Result: Returns first available phone number or default ``` #### How to Configure a Do While 1. Select "Do While" as your flow control type 2. Optionally set **Max Iterations** to cap how many times the loop can run (up to 1,000) 3. Open the sub-canvas and build the actions that should run each time round 4. Add a **Return** action inside the loop for the moment the loop should finish; its value becomes the loop's output 5. Add a **Continue** action wherever the loop should move on to the next iteration, optionally passing a value forward > πŸ’‘ Use Do While when you don't know in advance how many iterations you need, such as polling until something is ready or refining a result until it meets your criteria. The loop also outputs how many iterations it ran and the values passed by each Continue. > ⚠️ Continue is only available inside a Do While loop. Without a Return, set Max Iterations so the loop can't run forever. #### How to Use Return 1. Add "Return" where your workflow should finish with a result 2. Set the **value** to return, using variables from earlier steps as needed 3. In API workflows, this value becomes the response sent back to the caller, and you can optionally set the status code 4. In subworkflows, this value is handed back to the parent workflow #### How to Use Set Session Title 1. Add "Set Session Title" anywhere in your workflow 2. Provide the title, typically built from variables (for example, a customer name or order number) 3. The session is renamed, making runs much easier to find and identify in your session lists #### How to Use Track Metric 1. Define the metrics you want to measure in your project settings 2. Add "Track Metric" at the point in the workflow where the value is known 3. Choose the metric and provide its value: a number, text, yes/no, or one of a predefined set of options 4. Recorded values can then be analysed to monitor how your workflow performs over time > πŸ’‘ Track Metric is handy for measuring business outcomes, like order values processed or how often a request is rejected, not just technical health. ### Flow Control Connections #### How to Connect Flow Paths 1. **Locate Connection Points**: Each flow control path has circular connection points on the right side 2. **Drag to Connect**: Click and drag from connection point to target action 3. **Multiple Paths**: Different conditions can connect to different workflow sequences 4. **Path Convergence**: Separate paths can reconnect later in the workflow 5. **Visual Feedback**: Connections show as lines between actions #### How to Navigate Sub-Canvases 1. **Edit Buttons**: Click "Edit Loop" or "Edit Repeat" to open sub-canvas 2. **Breadcrumb Navigation**: Use breadcrumbs at top to navigate between canvases 3. **Variable Access**: Main workflow variables are available in sub-canvases 4. **Return Navigation**: Click main workflow name in breadcrumbs to return > πŸ’‘ Sub-canvases provide isolated space for flow control logic while maintaining access to parent workflow variables. ### Advanced Flow Control Techniques #### Variable Input Methods **Direct Values**: Type specific values like numbers, text, or boolean values **Workflow Variables**: Select variables using @ symbol or {{ }} notation\ **Calculated Values**: Use expressions to compute values dynamically **External Data**: Reference data from forms, APIs, or database queries #### Condition Building **Comparison Operators**: equals, not equals, greater than, less than, contains **Logical Operators**: AND, OR, NOT for complex multi-part conditions **Data Types**: Handle text, numbers, dates, boolean values appropriately **Variable References**: Use any variable from previous workflow steps #### Nesting Flow Controls **Nested Branches**: Place Branch controls inside Loop or Repeat controls **Loops within Conditions**: Different Branch paths can trigger different Loops **Complex Logic Trees**: Combine multiple flow controls for sophisticated decision making **Variable Scope**: Parent variables remain accessible in nested controls ### Important Considerations * Flow controls create sub-canvases accessible through "Edit" buttons * Variables from parent workflow are available within flow control sub-canvases * Branch conditions evaluate in order (If, then ElseIf conditions, finally Else) * Loop processing handles items individually and sequentially * Repeat executions are identical except for repetition counter variable * Get First Available Value stops at first non-empty value found * Connection points enable visual linking of different workflow paths * Performance impacts increase with large loops or high repetition counts > ⚠️ Be mindful of loop sizes and repetition counts as they can impact workflow execution time and resource usage. ### Flow Control Workflow Integration **Adding Flow Controls**: 1. Select appropriate flow control type based on logic requirements 2. Configure control parameters (conditions, items, repetitions, values) 3. Use "Edit" buttons to build internal workflow logic in sub-canvases 4. Connect flow control paths to different workflow sequences 5. Test logic with various input scenarios **Flow Control Results**: * Branch: Routes execution to different paths based on conditions * Loop: Processes all items and continues with results * Repeat: Completes specified repetitions and continues * Get First Available Value: Returns selected value as workflow variable **Variable Output**: Flow control results and internal variables become available for subsequent workflow actions, enabling complex data processing and decision-making throughout your automation. > πŸ’‘ Flow controls enable robust, adaptive workflows that handle real-world complexity - from simple conditional logic to sophisticated data processing and business rule implementation. Always test your flow control logic with various scenarios to ensure reliable operation. # Action Cards Action Cards are the fundamental building blocks of workflows in Lleverage. Each card represents a step in your automation process and contains configuration options specific to that action type. Understanding how to work with Action Cards is essential for creating effective workflows. ### Key Features * Consistent header structure across different action types * Variable outputs displayed in the top left corner * Interactive controls for testing and configuration * Natural language descriptions that update automatically * Connection points for linking actions together ### Action Card Anatomy Every Action Card includes these standard elements: **Header section** * Variable name in the top left (representing the action's output) * Expand/collapse chevron in the top right * Run button (play icon) to test the specific action * Three-dot menu for additional options **Body section** * Natural language description that updates based on configuration * Action-specific configuration fields * Connection points on left and right sides > πŸ’‘ Trigger cards are slightly different as they don't have play buttons or option menus, but they do include arrows to switch trigger types. ### How to Work with Action Cards #### How to Select an Action Card 1. Click on an Action Card to select it. 2. The selected card will display a purple border (the "purple glow" in Lleverage) and a deeper shadow effect. 3. Selection is required for certain operations such as using Co-Pilot. > πŸ’‘ Double-clicking a card will center it on your screen, making it easier to focus on a specific action. #### How to Move Action Cards 1. Select the Action Card you want to move. 2. Click and hold the card to drag it to a new position. 3. Release the card to place it in the new location. 4. The connections will automatically adjust to follow the card. > πŸ’‘ Moving cards helps you organise your workflow visually to better represent the logical flow. #### How to Resize Action Cards 1. Hover over the right edge of the card until you see the resize cursor. 2. Click and drag left or right to adjust the width. 3. Release when the card reaches your desired size. > ⚠️ Action Cards have a minimum width for accessibility purposes, so you cannot make them too narrow.

Resizing an Action Card

#### How to Test an Action Card 1. First, run the workflow once. The play button will only appear on non-trigger Action Cards after the workflow has been run. 2. Click the play button on the Action Card you want to test. 3. The action will execute using the current workflow variables that are available. 4. Values will flow into and out of the card as they would during a normal run. 5. The output will appear in the **Output Panel**, allowing you to check results. > πŸ’‘ Testing individual actions helps identify and resolve issues before they affect the entire workflow.

Test a indervidual Action

#### How to Expand or Collapse an Action Card 1. Click the chevron in the top right corner of the card. 2. When collapsed, the card shows only its header and natural language description. 3. When expanded, the card shows all configuration options. 4. Use collapse to save space when working with complex workflows.

Expand Action Card to see configuration

#### Input Expansion and Height Currently it is not possible to expand the overall height of an Action Card, but certain inputs can be expanded individually. 1. Hover over the bottom-right corner of an input field. 2. If an arrow icon appears (diagonal from top right to bottom left), click it to expand the input. 3. This gives you an expanded view of the input, which is most common in prompts and code boxes. 4. Many inputs also support auto-expanding height to fit content. > πŸ’‘ If you notice an input that does not expand properly, please let the Lleverage UK team know and we will aim to fix it. ### Important Action Card Considerations * The natural language description updates automatically based on your configuration. * Selected cards with the purple glow receive focus for Co-Pilot suggestions. * Each action type has different configuration options in the body section. * Card connections establish the sequence of execution in your workflow. * Cards can be rearranged at any time to change your workflow structure. > ⚠️ Workflows execute from left to right following the connections between cards. The arrangement and connections determine the execution path. # Action Connections Connecting actions in your workflow establishes the sequence of execution and creates the logical flow of your automation. Properly connected actions ensure that data flows correctly from one step to the next. ### Key Features * **Visual connection lines** between action cards * **Interactive connection points** for easy linking * **Multiple connection methods** for different workflow scenarios * **Left-to-right workflow direction** for logical progression * **Simple disconnection** when workflow changes are needed ### How to Connect Action Cards #### Method 1: Drag and Drop Connection 1. Identify the circle connection points on the left and right sides of action cards 2. Click and hold on a connection point 3. Drag to the connection point of another action card 4. Release to create the connection 5. A line will appear between the cards, showing they are connected > πŸ’‘ This method works well when you already have multiple cards on your canvas that need to be connected. #### Method 2: Add Connected Actions 1. Hover over a circle on an existing action card 2. Click on the circle to open the Add Action menu 3. Select an action type from the menu 4. The new action will be added to your canvas already connected to the original card > πŸ’‘ This method is efficient for building your workflow step by step, as each new action is automatically connected. #### Method 3: Using the Plus Icon 1. For cards that aren't connected yet, look for the plus icon on the right side 2. Click this plus icon to open the Add Action menu 3. Select an action to add to your workflow 4. The new action will appear connected to the original card > πŸ’‘ The plus icon provides a visual indicator of where new connected actions can be added. ### How to Disconnect Actions 1. Click on the middle of a connection line between two action cards 2. A red circle with a white cross will appear 3. Click on this delete icon to remove the connection 4. The cards will remain on your canvas but will no longer be connected in the workflow > ⚠️ Disconnecting actions will break your workflow path. Make sure to reconnect or create alternative paths as needed. ### Important Connection Considerations 1. **Workflow Direction**: * Workflows generally execute from left to right * Connections should follow this direction for clear, logical flow 2. **Multiple Connections**: * Some actions (like branches) can have multiple output connections * Most actions have a single input and a single output connection 3. **Connection Visualization**: * Lines between cards represent the flow of data and execution * The system automatically adjusts connection lines when you move cards 4. **Workflow Validation**: * Disconnected actions may cause workflow validation errors * Every action (except outputs) should connect to something else * Every action (except triggers) should have something connected to it 5. **Branching Workflows**: * For conditional paths, use Branch actions to create multiple routes * Each branch can connect to different subsequent actions > πŸ’‘ A properly connected workflow forms a complete path from trigger to output, ensuring that your automation runs as expected. ### Tips for Effective Workflow Connections 1. Arrange your cards logically from left to right to match execution flow 2. Use the canvas controls to reorganize connected cards for better visualization 3. Test connections by running the workflow to ensure data flows correctly 4. For complex workflows, consider using subworkflows to manage connections 5. Review your workflow for any disconnected actions before publishing > ⚠️ Remember that the connections between actions determine not just the sequence of execution but also how data is passed between steps in your workflow. # Run Panel ### Testing and Debugging Workflows The Run Panel in Lleverage allows you to test your workflows before publishing them. Located in the top right corner of your screen, this powerful feature lets you execute your workflow, view the process in real-time, examine detailed traces, and debug issues with AI assistance. ### Run Panel Tabs The run panel is organised into four tabs: * **Run**: Execute your workflow with test inputs, watch it progress in real time, and inspect traces. Everything on this page happens in the Run tab. * **Feedback**: Review the thumbs up / thumbs down feedback your end users leave on runs. You can filter the feedback list, mark items as resolved, replay the session behind a piece of feedback, create a test directly from it, or export feedback to a data table for further analysis. * **Test**: Build and run automated tests that check your workflow's outputs against criteria. See the [Tests](/publishing-guide/tests) page for the full guide. * **Publish**: Manage your workflow's draft and published versions. See the [Publishing Workflows](/publishing-guide/publishing-workflows) page for the full guide. ### Key Features * Real-time workflow execution and visualization * Input field generation based on trigger type * Detailed trace information with inputs, outputs, and timing * AI-powered error fixing with Copilot integration (temporarily unavailable while the Copilot is being improved) * History of previous runs for comparison * Ability to edit and rerun with different inputs * Response rating system for workflow improvement * Output display with copy functionality ### **How to Access the Run Panel** 1. Create or open a workflow in the Canvas 2. Ensure there are no errors in your workflow (the Run button will be purple when ready) 3. Click the "Run" button in the top right corner of your screen 4. The Run Panel will open as a modal window > πŸ’‘ The Run button will be highlighted in purple when your workflow is error-free and ready to test.

Run Panel

### **How to Test Your Workflow** 1. When the Run Panel opens, you'll see input fields based on your trigger type 2. Fill in the required information or click "Generate Inputs" for sample data 3. Click "Submit" or "Run Workflow" to execute the test 4. Watch as each node in your workflow processes in real-time with progress indicators 5. Review the output displayed at the bottom of the panel > πŸ’‘ You can see each node activate on the canvas as the workflow executes, giving you a visual representation of the data flow.

Run button

### **How to View and Analyze Traces** 1. After running your workflow, you'll see progress indicators showing the execution of each node 2. Click to expand any trace to view detailed information: * Input data for that specific node * Output data generated by the node * Execution time for the step * For AI steps: the thinking process behind the response 3. Copy data in various formats including JSON for further analysis 4. Use trace information to debug and optimize your workflow performance > πŸ’‘ Traces provide comprehensive insight into how your workflow processes data at each step, making debugging much more effective. ### **How to Fix Errors with AI Assistance** > ⚠️ The Copilot fix options below are temporarily unavailable while the Workflow Copilot is being improved. In the meantime, fix errors manually using the error message and the trace details. 1. If your workflow encounters an error during execution, an error message will appear 2. You'll see one of two Copilot fix options: * **"Get Copilot to Fix it and Run"**: AI fixes the workflow and automatically reruns it * **"Get Copilot to Fix it"**: AI fixes the workflow, but you must manually run it again 3. Click your preferred option to let the AI analyze and resolve the issue 4. Review the changes made by Copilot before proceeding > ⚠️ Always review AI-suggested fixes to ensure they align with your workflow's intended functionality. ### **How to Rate and Improve Responses** 1. After a workflow run completes, locate the response rating options at the bottom of the output 2. Mark responses as "Good Response" or "Bad Response" based on quality 3. Use this feedback to track workflow performance over time 4. Consider making adjustments to workflows that consistently receive poor ratings ### **How to Create New Tests and Rerun** 1. **To create a new test**: Click "New" at the bottom right to start fresh with empty inputs 2. **To rerun with same inputs**: Click "Run Again" at the bottom right 3. **To create a test from current output**: Click "Create Test" to save current configuration as a reusable test case ### How to View Previous Runs 1. Click the dropdown arrow next to "Run Workflow" in the top left corner of the Run Panel 2. Select from the list of previous runs to view their inputs and outputs 3. Compare different runs to analyze how changes affect your workflow > πŸ’‘ Each run is recorded separately, making it easy to track the performance of different versions of your workflow.

Revisiting last runs

### **How to Edit and Rerun a Test** 1. View a previous run from the dropdown menu 2. Click the "Edit" button to modify the inputs 3. Make your changes to the input values 4. Click "Submit" to run the workflow with the new inputs 5. A new run will be logged with your updated inputs and traces > ⚠️ Editing a previous run doesn't overwrite it - instead, it creates a new run with the modified inputs. ### **How to Copy Output Data** 1. Navigate to the output section at the bottom of the Run Panel 2. Click the "Copy" button next to the output you want to save 3. The output will be copied to your clipboard for use elsewhere 4. Use copied data for documentation, sharing results, or further processing ### **How to Reset the Run Panel** 1. Click the "Reset" button in the top right corner of the Run Panel 2. The panel will clear all inputs and return to its initial state 3. You can now start a fresh test with new inputs

How to reset test

### **Next Steps After Testing** 1. Once you're satisfied with your workflow's performance in the Run Panel 2. Review all traces to ensure optimal performance 3. Address any consistently poor-rated responses 4. Click "Publish" to make your workflow available for deployment 5. Follow the publishing process to complete the deployment > ⚠️ Thorough testing in the Run Panel, including trace analysis and error resolution, is essential before publishing to ensure your workflow functions optimally in a live environment. # Variables and Data Flow Variables in Lleverage allow you to pass information between different nodes in your workflow. Unlike many other automation platforms, Lleverage's variable system provides exceptional flexibility in how you structure the passing of inputs, outputs, and other elements throughout your workflow. ### Key Features * Pass data dynamically between workflow nodes * Visual representation with color-coded chips * Two methods of implementation: user-friendly (@) and advanced ({{ }}) * Connect nodes to access their variables * Automatic variable name updates when nodes are renamed * Support for nested data and arrays ### How to Use Variables with the @ Method 1. Click on any input field where you want to use a variable 2. Look for the @ button at the bottom of the field 3. Click the @ button to open the variable dropdown panel (you cannot type @ on your keyboard to access this) 4. Select the node containing your desired variable (shown as color-coded pills with node name and icon) 5. Choose the specific output you need from that node > πŸ’‘ The color of the icon represents the subcategory of that action type, making it easier to identify the source of variables.

Variants with advanced open

### How to Use Variables with the {{ }} Method (Advanced) 1. Click on any input field where you want to use a variable 2. Type two opening curly braces {{ to start the variable reference 3. Enter the node name followed by a dot (.) 4. Continue with the specific property path you want to access 5. Close with two closing curly braces }} > πŸ’‘ The advanced method gives you more detailed access to specific properties within complex data structures.

Advanced Variables

### How to Connect Nodes for Variable Access 1. Ensure there is a connection line between the source node and the destination node 2. Connections can be direct or through intermediate nodes 3. Without a connection, variables from the source node won't be available > ⚠️ Even if nodes are connected with lines, you still need to explicitly specify the variable in your destination node for the data to pass through.

Connected Nodes

### How to Work with Nested Data 1. Access nested information using the @ method by navigating through levels in the dropdown 2. For the {{ }} method, use dot notation: {{customerData.address.city}} 3. Access array elements by selecting them in the dropdown or using bracket notation: {{orderItems\[0].price}} > πŸ’‘ For advanced use cases, the variable dropdown has an "Advanced" section that shows more detailed options. ### How to Check Available Variables 1. Run your workflow at least once to populate the variable data 2. Click on a node where you want to use variables 3. Open the variable selection with the @ button 4. Browse through the available variables organized by source node > ⚠️ Variables with broken references (if a source node is removed) will show an error in your workflow. ### How to Work with Database Connection Strings 1. Database connection strings are managed through Secrets or Connections 2. Select a connection string from the dropdown when setting up a database connection 3. If needed, manually enter a connection string by clicking the icon next to the selection > πŸ’‘ For most use cases, stick with the standard variable output of nodes. AI nodes can help translate information as needed. # Error Handling and Validation Lleverage provides comprehensive error handling and validation to ensure your workflows run smoothly. The platform proactively identifies configuration issues before you run or publish your workflows, saving you time and preventing runtime failures. ### Key Features * Real-time validation of action card configurations * Visual indicators for error locations * Detailed error messages with solutions * Error handling within the Run Panel * Multiple ways to fix issues (manual; Copilot assistance is temporarily unavailable while it is being improved) * Fallback error management for runtime issues

Validation on canvas

Information on Error message

> πŸ’‘ The validation system works continuously as you build your workflow, catching issues before you attempt to run or publish. ### How to View Error Details 1. Hover over the error notification in the top right corner 2. Click on a specific error to navigate directly to the issue 3. Alternatively, locate action cards with blue outlines in your workflow 4. Hover over the "i" icons next to field labels to see detailed error messages > πŸ’‘ Error messages will explain exactly what's wrong and what you need to do to fix the issue. ### How to Fix Validation Errors 1. Read the error message to understand the specific requirement 2. Make the necessary changes to the configuration as suggested 3. Check if the blue outline disappears, indicating the error is resolved 4. Repeat for any remaining errors in your workflow > ⚠️ Common issues include missing required fields, incorrect data formats, or missing authentication for external providers. ### How to Use Copilot for Error Resolution > ⚠️ Copilot error resolution, including the "Auto Fix" button, is temporarily unavailable while the Workflow Copilot is being improved. Use the manual fix steps above in the meantime. 1. Identify an error in your workflow 2. Click the "Auto Fix" button or tell Copilot about the error 3. Copilot will suggest changes to resolve the issue 4. Review the suggested fix and apply it if appropriate > ⚠️ Copilot cannot handle authorization to external providers or log you into services - these actions must be completed manually. ### How to Handle Runtime Errors 1. If an error occurs during workflow execution, an error panel will appear 2. Read the detailed error message to understand the issue 3. Choose one of the following options: * Fix the issue manually based on the error message * Click "Auto Fix" to let Copilot solve the problem (temporarily unavailable) * Tell Copilot how you'd like to fix the workflow (temporarily unavailable) > πŸ’‘ Runtime errors often reveal edge cases or conditions that weren't apparent during the building process. ### Where to Find Error Indicators Lleverage shows errors in multiple locations to ensure you don't miss them: 1. In the top bar as notification chips 2. In the publish panel when attempting to publish 3. In the run panel when testing your workflow 4. On the action cards themselves (blue outlines) 5. Next to specific field labels within action cards > ⚠️ Authentication issues with external providers are common errors that require manual resolution - the system will guide you through what needs to be done. # Co-Pilot Best Practices Co-Pilot is available through the Workflow Canvas and is designed to help you build workflows faster. It can suggest actions, fix issues, and guide you step by step. These best practices will help you get the most out of it. ### Be Specific with Your Prompts * When asking Co-Pilot to add or change something, be clear about the node or action you want to work with * If you do not already have the node selected, name it specifically in your prompt * For example, say *β€œExtract the email address from the Gmail trigger and add it to the Google Sheets action”* rather than just *β€œExtract the email”* ### Think Step by Step * Imagine you are drawing the workflow on a whiteboard * Think about the flow systematically: * How the data is ingested into the workflow * How the data moves through nodes inside the workflow * How the data is outputted at the end * The clearer you are about each step, the better Co-Pilot can build what you need ### Avoid Ambiguity * Do not leave instructions open to interpretation * Instead of saying *β€œConnect this to that”*, specify exactly what fields and outputs should be connected * Precise language avoids errors and saves time later ### Use Co-Pilot as a Guide * Co-Pilot is not just for creating nodes * You can ask it to explain what a workflow is doing * You can ask it to suggest improvements * You can use it to debug issues step by step ### Review Suggested Changes * Co-Pilot shows you every change it has made, labelled as Added, Edited, or Deleted * Expand a change to see the detail of exactly what was altered * If you do not like a particular change, undo it individually without discarding the rest ### Watch for Validation and Fixes * Co-Pilot can highlight areas where validation is needed inside your workflow * Keep an eye out for these prompts, as they help prevent broken runs * You can also use Co-Pilot to fix errors directly, saving time on manual troubleshooting > πŸ’‘ Think of Co-Pilot as a partner. It builds, explains, fixes, and suggests, but you are still in control of how your workflow works. # Publishing Workflows Publishing a workflow in Lleverage creates a numbered version and makes it available for use based on its trigger type. Your edits on the canvas build up as a draft, and publishing turns that draft into the live version, so you can keep working without affecting what users see. ### Key Features * Draft and published versions with clear badges * Minor or major version numbering when you publish * AI-suggested version comments describing what changed * Publish, unpublish, and revert per version * Different deployment options based on trigger type * Public or Private visibility for app links * Embed codes and API endpoints for integration into other applications ### Drafts and Versions As soon as you change a published workflow, a new draft is created. In the Publish panel you'll see your versions listed: * **Draft**: your unpublished changes, marked with a Draft badge * **Published versions**: numbered versions, with the currently live one clearly indicated > πŸ’‘ The draft is yours to experiment with. End users keep using the last published version until you publish again. ### How to Publish Your Workflow 1. First, test your workflow using the Run Panel to ensure it works as expected 2. Click the "Publish" button in the top right corner of your screen 3. Review any validation messages that appear (fix any issues if necessary) 4. Choose a **minor** or **major** version bump: minor for small tweaks, major for significant changes 5. Add a version comment describing the change. Lleverage suggests one for you based on what changed, which you can accept or edit. 6. Confirm to publish. The new version goes live and appears in your version list. ### How to Manage Versions **To unpublish a version:** 1. Open the Publish panel 2. Find the published version and choose unpublish 3. The workflow is no longer available to users until you publish again **To revert to an earlier version:** 1. Open the Publish panel and find the version you want to go back to 2. Choose revert to bring the canvas back to that version's state 3. Publish when you're ready to make it live again **To discard your draft:** 1. Open the Publish panel while you have unpublished changes 2. Choose discard draft to throw away the draft and return to the last published version > ⚠️ Discarding a draft removes your unpublished changes, so make sure you no longer need them. ### App Visibility: Public or Private Workflows with an App trigger can be published as **Public** or **Private**: * **Public**: anyone with the link can open and use the app * **Private**: only signed-in members of your workspace can use it The visibility is configured on the App trigger, and the Publish panel shows the matching links: a public link when the app is Public, and an internal workspace link either way. ### How to Publish Different Trigger Types **App Trigger (form or chat):** 1. The Publish panel displays your app links: the internal workspace link and, for Public apps, the public link 2. Copy a link to share with users 3. Click "Get Code" to access embed code for integrating the app into other websites **API Call Trigger:** 1. The Publish panel displays an API endpoint 2. Copy the endpoint URL for API integration 3. View code examples in Node.js, Python, PHP, and Go 4. No app link is provided (API calls don't have user interfaces) **Schedule Trigger:** 1. The Publish panel displays schedule information 2. View when the workflow will run automatically 3. No user interface or shareability options are provided **Integration Trigger:** 1. The Publish panel displays information about the integration 2. Similar to scheduled triggers, there is no user interface to share > ⚠️ Schedule and Integration triggers run automatically from Lleverage's backend and don't have user interfaces to share. ### How to Embed Workflows in External Applications **Using HTML Embed Code:** 1. Publish your workflow with an App trigger 2. Click "Get Code" in the Publish panel to access the embed code 3. Copy the provided HTML iframe code 4. Paste the code into your website, web application, or development project 5. The embedded workflow will function identically to the standalone app **Using API Integration:** 1. Publish your workflow with an API Call trigger 2. Copy the API endpoint from the Publish panel 3. Choose from the provided code examples (Node.js, Python, PHP, Go) 4. Implement the API call in your development environment 5. Include the bearer token for authorisation as configured in your platform settings > πŸ’‘ When embedded via iframe, the workflow functions exactly as it does when accessed directly through the app links. > ⚠️ API integrations require a development environment and cannot be simply opened as HTML files in a web browser like embedded forms and chats. # API Endpoint API Endpoints in Lleverage allow you to trigger workflows programmatically from your own applications. When you create a workflow with an API Call trigger, you can publish it to generate an endpoint that can be called from external systems. ### Key Features * Programmable access to your Lleverage workflows * Secure authentication with Lleverage API tokens * Support for file uploads and mixed data types * Code examples in multiple programming languages * Dynamic code generation based on workflow configuration * Custom integration into your existing applications ### How to Create an API Endpoint 1. Start by creating a workflow with an **API Call** trigger 2. Configure the required fields in the trigger settings: * For file uploads, set the field type to **File** * Add any additional fields (text, number, etc.) * Configure authentication requirements 3. Build your workflow with the desired actions 4. Test your workflow using the Run Panel 5. Click the **Publish** button in the top right corner 6. The Publish Panel will display your API endpoint URL πŸ’‘ Read more about different trigger types in the Triggers documentation page. ### How to View Code Examples 1. Publish your workflow with an API Call trigger 2. In the Publish Panel, locate the **Get Code** button 3. Click the button to view code examples 4. Select from available programming languages: * cURL * Node.js * Python * PHP (Laravel) * Go πŸ’‘ These code examples are dynamically generated based on your workflow's field configuration. ### API Code Examples #### cURL ```bash curl -X POST "https://your-workflow.lleverage.run/your-endpoint" \ -H "Authorization: Bearer {YOUR_TOKEN}" \ -H "Content-Type: application/json" \ -d '{"field1": "value1", "field2": "value2"}' ``` #### Node.js ```javascript const response = await fetch("https://your-workflow.lleverage.run/your-endpoint", { method: "POST", headers: { "Authorization": "Bearer YOUR_TOKEN", "Content-Type": "application/json" }, body: JSON.stringify({ "field1": "value1", "field2": "value2" }) }); if (!response.ok) { throw new Error("Failed to fetch data"); } const data = await response.json(); console.log(data); ``` #### Python ```python import requests headers = { "Authorization": "Bearer YOUR_TOKEN" } response = requests.post( "https://your-workflow.lleverage.run/your-endpoint", headers=headers, json={ "field1": "value1", "field2": "value2" } ) print(response.json()) ``` #### PHP (Laravel) ```php use Illuminate\Support\Facades\Http; $response = Http::withToken('YOUR_TOKEN') ->post("https://your-workflow.lleverage.run/your-endpoint", [ "field1" => "value1", "field2" => "value2" ]); $data = $response->json(); print_r($data); ``` #### Go ```go package main import ( "bytes" "encoding/json" "fmt" "io/ioutil" "net/http" ) func main() { data := map[string]string{ "field1": "value1", "field2": "value2" } payload, _ := json.Marshal(data) req, _ := http.NewRequest("POST", "https://your-workflow.lleverage.run/your-endpoint", bytes.NewBuffer(payload)) req.Header.Add("Authorization", "Bearer YOUR_TOKEN") req.Header.Add("Content-Type", "application/json") client := &http.Client{} response, _ := client.Do(req) defer response.Body.Close() body, _ := ioutil.ReadAll(response.Body) fmt.Println(string(body)) } ``` ### Starting Workflows Asynchronously Use the `/async` endpoint variant when the calling system only needs to start the workflow, not wait for the workflow result. To use it, send a POST request to the published API endpoint with `/async` appended. Use the same non-file JSON fields as the standard endpoint. ```bash curl -X POST "https://your-workflow.lleverage.run/your-endpoint/async" \ -H "Authorization: Bearer {YOUR_TOKEN}" \ -H "Content-Type: application/json" \ -d '{"field1": "value1", "field2": "value2"}' ``` Lleverage accepts the request, schedules the workflow to run in the background, and returns an immediate JSON acknowledgement: ```json { "id": "...", "message": "OK" } ``` The `id` identifies the scheduled task. The acknowledgement only confirms that the workflow was accepted for asynchronous execution. It is not the workflow response or output. This is useful for: * Fire-and-forget workflow starts * Avoiding client timeouts for longer workflows * Webhooks or integrations that only need to enqueue work * Workflows where the result is tracked elsewhere, such as in Lleverage activity, a data table, a notification, or another system updated by the workflow Use the standard API endpoint instead when the caller needs the workflow result synchronously. #### Limitations * The HTTP caller does not receive the workflow response or output. * Files are not supported through the async HTTP call, including file upload fields and file responses. Use the standard endpoint when the request or response needs files. * Errors that happen after the workflow has been accepted are not returned to the original HTTP caller. Check workflow activity and logs for execution results. * If validation or scheduling fails before the workflow is accepted, the async request can still return an HTTP error. ### How to Send Files via API When your workflow includes file fields, you'll need to use multipart/form-data encoding: #### cURL with File Upload ```bash curl -X POST "https://your-workflow.lleverage.run/your-endpoint" \ -H "Authorization: Bearer {YOUR_TOKEN}" \ -F "file=@/path/to/your/file.ext" \ -F "field1=value1" \ -F "field2=value2" ``` #### Node.js with File Upload ```javascript const FormData = require('form-data'); const fs = require('fs'); const form = new FormData(); form.append('file', fs.createReadStream('/path/to/file.ext')); form.append('field1', 'value1'); form.append('field2', 'value2'); const response = await fetch("https://your-workflow.lleverage.run/your-endpoint", { method: "POST", headers: { ...form.getHeaders(), "Authorization": "Bearer YOUR_TOKEN" }, body: form }); ``` #### Python with File Upload ```python import requests files = {'file': open('/path/to/file.ext', 'rb')} data = {'field1': 'value1', 'field2': 'value2'} headers = {'Authorization': 'Bearer YOUR_TOKEN'} response = requests.post( "https://your-workflow.lleverage.run/your-endpoint", files=files, data=data, headers=headers ) print(response.json()) ``` #### PHP (Laravel) with File Upload ```php use Illuminate\Support\Facades\Http; $response = Http::withToken('YOUR_TOKEN') ->attach( 'file', // Field name file_get_contents('/path/to/file.ext'), // File contents 'file.ext' // Filename )->post("https://your-workflow.lleverage.run/your-endpoint", [ "field1" => "value1", "field2" => "value2" ]); $data = $response->json(); ``` ### How to Structure API Requests 1. Use the endpoint URL provided in the Publish Panel 2. Include your Lleverage API token in the Authorization header (if required) 3. Structure your request body to include all fields defined in the trigger 4. For file uploads, use multipart/form-data encoding 5. Send the request using your preferred programming language or API client ⚠️ Always include all fields specified in the trigger configuration, even if you're not using them in your workflow. Missing required fields will cause the API call to fail. ### How to Test API Endpoints 1. Use the provided code examples as a starting point 2. Modify the example with your actual API endpoint and token 3. Run the code from your development environment 4. Monitor the response to ensure successful workflow triggering 5. Check your workflow execution in the Lleverage platform πŸ’‘ Use tools like Postman or Insomnia to test your API endpoints before implementing them in your application. ### Troubleshooting Common Issues 1. **401 Unauthorized** * Verify your API token is correct and active * Ensure the Authorization header is properly formatted: `Bearer YOUR_TOKEN` 2. **400 Bad Request** * Check that all required fields are included * Verify field types match your workflow configuration * For file uploads, ensure proper multipart encoding 3. **413 Payload Too Large** * Check file size limits for your Lleverage plan * Consider compressing files before upload 4. **Empty or Unexpected Response** * Ensure your workflow has proper output configuration * Check workflow logs in Lleverage for processing errors ### Best Practices * Store API tokens as environment variables * Implement retry logic for transient failures * Validate file types and sizes before sending * Log API responses for debugging * Monitor workflow execution logs regularly * Use HTTPS for all API communications * Handle errors gracefully in your application ⚠️ Be mindful of rate limits based on your Lleverage plan. # Chat App When you create a workflow with a Chat trigger in Lleverage, you can publish it as a standalone chat application with its own dedicated URL. This allows you to share conversational interfaces with users without requiring them to access the Lleverage platform directly.

Chat Publish Panel

### Key Features * Two dedicated URL options for your chat application * Similar functionality to the Run Panel but externally accessible * Logo customization options * Shareable with anyone via direct link * Embed code for website integration * Potential for advanced customization through Solutions Assistance ### How to Create a Chat Application 1. Create a workflow with a "Chat" trigger 2. Configure your workflow with the desired conversational logic 3. Test the workflow using the Run Panel 4. Click the "Publish" button in the top right corner 5. Your chat application is now live with its own URLs > πŸ’‘ Chat applications work similarly to the Run Panel but are accessible to external users through dedicated links. ### How to Access Your Chat Application URLs 1. Publish your workflow with a Chat trigger 2. The Publish Panel will display two app links: * **Lleverage Link**: Your chat app within the Lleverage workspace * **External App Link**: A standalone external link to your chat app 3. Copy either URL to share with users 4. Anyone with the links can interact with your chat application > πŸ’‘ Both app links provide dedicated interfaces for users to interact with your workflow through chat. ### How to Get Embed Code for Your Chat 1. Publish your workflow with a Chat trigger 2. In the Publish Panel, click the "Get Code" button 3. Copy the provided embed code 4. Paste the code into your website or application 5. Your chat interface will be embedded and fully functional > πŸ’‘ When embedded via iframe, the chat functions exactly as it does when accessed directly through the app links. ### How to Customize Your Chat Application 1. Publish your workflow with a Chat trigger 2. In the Publish Panel, locate and click the "Customize" button 3. Upload your logo to brand the chat interface 4. Save your customization settings 5. Your branded chat application is now ready to share > πŸ’‘ Adding your logo helps create a more professional and branded experience for users. ### How to Share Your Chat Application 1. Choose between the Lleverage link (within workspace) or External App link (standalone) 2. Copy your preferred link from the Publish Panel 3. Share the link directly with users via email, messaging, or other channels 4. Users can access the chat application from any web browser 5. No Lleverage account is required for users to interact with your chat ### How to Request Advanced Customization 1. For more advanced customization options beyond the standard offerings 2. Contact Lleverage's Solutions Assistance team 3. Describe your specific requirements for the chat application 4. The team can provide tailored solutions for your needs > πŸ’‘ Lleverage is continuously improving the customization options for chat applications, so check for updates regularly. ### Best Practices for Chat Applications 1. Keep conversations focused and goal-oriented 2. Test your chat workflow thoroughly before sharing 3. Consider adding helpful prompts to guide users 4. Review chat interactions periodically to improve your workflow 5. Use clear, concise language in your chat responses > ⚠️ Remember that anyone with your chat application URLs can access them, so consider authentication needs for sensitive information. # Form App When you create a workflow with a Form trigger in Lleverage, you can publish it as a standalone form application with its own dedicated URL. This allows you to collect structured inputs from users and process them through your workflow.

Form Publish Panel

## Form Applications When you create a workflow with a Form trigger in Lleverage, you can publish it as a standalone form application with its own dedicated URLs. This allows you to collect structured inputs from users and process them through your workflow. ### Key Features * Two dedicated URL options for your form application * Configurable input fields with validation options * Required field capabilities for ensuring complete data collection * Embed code for integration into existing websites * Similar functionality to Chat applications but with structured inputs * **URL parameter pre-filling** β€” pass values via the URL to automatically populate form fields ### How to Create a Form Application 1. Create a workflow with a "Form" trigger 2. Configure your input fields in the trigger settings 3. Set fields as required or optional based on your needs 4. Build your workflow to process the form submissions 5. Test the workflow using the Run Panel 6. Click the "Publish" button in the top right corner > πŸ’‘ Forms are ideal for collecting structured information that needs to follow a specific format. ### How to Access Your Form Application URLs 1. Publish your workflow with a Form trigger 2. The Publish Panel will display two app links: * **Lleverage Link**: Your form app within the Lleverage workspace * **External App Link**: A standalone external link to your form app 3. Copy either URL to share with users 4. Anyone with the links can access and submit your form > πŸ’‘ Both app links provide dedicated interfaces for users to interact with your workflow through a structured form. ### Pre-filling Forms with URL Parameters You can pre-fill form fields by appending URL parameters to your app link using **bracket notation**: ``` https://app.lleverage.ai//w/?i[fieldName]=value ``` **Example:** If your form has fields called `machine` and `model`: ``` https://app.lleverage.ai/xukfwbfwk/w/y8jbih5h?i[machine]=ficep&i[model]=coolaid ``` When users open this link, the `machine` field will show "ficep" and the `model` field will show "coolaid" β€” already filled in and ready to submit or adjust. **How it works:** * URL parameter keys are matched to form field names * Matching fields have their default values set automatically * Non-matching parameters are silently ignored * Users can still edit pre-filled values before submitting **Common use cases:** * Linking from an ERP with article numbers or order references pre-filled * Creating per-client URLs with customer-specific defaults * Embedding parameters in QR codes for factory or warehouse scanning * Including pre-filled links in email templates to reduce manual entry > πŸ’‘ For full details on URL parameter syntax and how they flow through the App Trigger, see the [URL Parameters section in the Triggers documentation](/canvas-actions/triggers#app-trigger-url-parameters). > ⚠️ URL parameters are visible in the browser address bar. Avoid passing sensitive data through URL parameters. ### How to Get Embed Code for Your Form 1. Publish your workflow with a Form trigger 2. In the Publish Panel, click the "Get Code" button 3. Copy the provided embed code 4. Paste this code into the HTML of your website 5. The form will now appear directly on your website > πŸ’‘ Embedding forms in your website creates a seamless experience for your users without redirecting them to another page. ### How to Configure Required Fields 1. Create or edit a workflow with a Form trigger 2. Configure your input fields in the trigger settings 3. Enable the "Required" option for fields that must be completed 4. Users will be prompted to complete these fields before submission > ⚠️ Be mindful about which fields you mark as required. Only make fields required if they are truly necessary for your workflow to function properly. ### How to Customize Your Form Application 1. Publish your workflow with a Form trigger 2. In the Publish Panel, locate and click the "Customize" button 3. Upload your logo to brand the form interface 4. Save your customization settings 5. Your branded form application is now ready to share > πŸ’‘ Adding your logo helps create a more professional and branded experience for users. ### How to Share Your Form Application 1. Choose between the Lleverage link (within workspace) or External App link (standalone) 2. Copy your preferred link from the Publish Panel 3. Share the link directly with users via email, messaging, or other channels 4. Users can access the form application from any web browser 5. No Lleverage account is required for users to interact with your form ### Best Practices for Form Applications 1. Keep forms concise and focused on collecting necessary information 2. Provide clear labels and placeholder text for each field 3. Use validation to ensure data quality 4. Test your form thoroughly before sharing it with users 5. Consider the user experience and minimize the number of required fields 6. Use URL parameters to pre-fill known values and reduce user effort > ⚠️ Remember that anyone with your form application URLs can access them, so consider authentication needs for sensitive information. # Tests Build reliable workflows by creating automated tests that validate your outputs against specific criteria. Tests help ensure your workflows perform consistently across different inputs and edge cases. ### Overview Tests validate workflow outputs automatically by checking them against a list of criteria you define. When you create a test, Lleverage saves the inputs from your run as a fixture and can replay them to check whether your workflow still meets your requirements after making changes. Key features: * Automatic input capture from workflow runs * Plain-language criteria, checked individually * Passed / Failed results with a confidence indicator * An AI evaluation model of your choice judges the output * Tests can be generated from end-user feedback * Run your whole test suite in one go ### How to Access Tests 1. Open the run panel from the top right corner of the canvas 2. Select the **Test** tab 3. Your test suite appears, with options to create your first test if none exist yet ### How to Create a Test from a Run 1. After running your workflow, click **Create Test** on the run output 2. The test creation form appears pre-filled with your run data 3. **Choose the variable to evaluate**: pick which workflow output the test should check 4. **Write your criteria**: add one or more plain-language statements that should be true about the output, for example "The extracted text contains a person's name". Each criterion can be edited, added, or removed individually. 5. **Pick an evaluation model**: choose which AI model judges whether the output meets your criteria 6. Save the test to add it to your suite, or save and run it straight away > πŸ’‘ **Tip**: Tests automatically capture and store the inputs from your original run as a fixture, so you can replay the exact same scenario as often as you like. ### How to Create Tests from Feedback 1. Open the **Feedback** tab in the run panel 2. Find a piece of end-user feedback worth turning into a regression check 3. Click **Create Test** on the feedback item 4. The test is set up from that session's inputs, ready for you to refine the criteria > πŸ’‘ Feedback-driven tests are a quick way to make sure a problem an end user hit never comes back. ### Understanding Test Results * **Passed**: the output met your criteria * **Failed**: one or more criteria were not met * **Confidence indicator**: alongside the result, a Low, Medium, or High confidence label shows how certain the evaluation was. Low confidence usually means the criteria are ambiguous or the output was unclear, so consider tightening the wording. * **Per-criterion detail**: each criterion is judged individually, so you can see exactly which ones passed or failed * **View the session**: open the session behind a test result to inspect the full run that produced the output ### How to Work with Fixtures A test's fixture is the saved set of inputs it replays. 1. Open a test and edit its fixture to change the inputs it runs with 2. Preview the fixture to check what the test will actually send before running it 3. To test a different scenario, duplicate the test and give the copy its own fixture ### How to Manage Existing Tests **To run a test again:** 1. Select the test you want to re-run 2. Click **Run** to execute it with its stored fixture 3. Compare results to see if your workflow changes improved things **To run all tests:** 1. Use the run all option at the top of your test suite 2. Every test executes against the current workflow 3. Review the pass and fail counts to spot regressions **To edit a test:** 1. Select the test you want to modify 2. Update the criteria, the variable being evaluated, the evaluation model, or the fixture 3. Save your changes **To delete a test:** 1. Select the test you want to remove 2. Click **Delete** and confirm ### How to Build Comprehensive Test Suites 1. **Test different input types**: Create tests for the various data formats your workflow might receive 2. **Test edge cases**: Include unusual or extreme inputs that might break your workflow 3. **Test business logic**: Validate that your workflow handles different business scenarios correctly 4. **Run all tests together**: Execute your entire suite after making changes to catch regressions early > πŸ’‘ **Best Practice**: For complex business processes, create multiple tests with different fixtures to ensure your workflow handles all possible scenarios reliably. Tests are essential for maintaining workflow reliability, especially when making changes or handling complex business processes with varied input types. # Integration Configuration Integration Triggers in Lleverage allow your workflows to run automatically based on events from external systems. Once configured, these triggers can be activated to respond to external events in real-time, providing automated responses without manual intervention. ### Key Features * Automatic workflow execution based on external events * Schedule information for monitoring trigger execution * Mock testing capabilities with sample data * Ability to toggle triggers on and off * Backend automation that runs without user intervention ### How to Test Integration Triggers 1. Select your already-configured Integration trigger in the workflow 2. Go to the Run Panel in the top right corner 3. The Run Panel will display input options and sample data 4. Use the dropdown to select mock data for testing 5. Click "Run Workflow" to test how it handles the sample data 6. Review the results to ensure proper functionality > πŸ’‘ Testing with mock data allows you to verify your workflow logic before activating it for real external events. ### How to Activate and Deactivate Integration Triggers 1. After your workflow with an Integration trigger is ready for use 2. Click the "Publish" button in the top right corner 3. The Publish Panel will open, showing the activation toggle 4. Toggle the switch ON to activate your integration trigger 5. Toggle the switch OFF to deactivate it temporarily 6. The activation status is also visible in the top bar of the editor > ⚠️ When active, integration triggers will automatically run your workflow whenever the specified event occurs, which may consume workflow runs from your plan. ### How to Monitor Integration Trigger Execution 1. After publishing, check the Publish Panel for scheduling information 2. This information shows when your integration is scheduled to check for events 3. To view past executions, go to the workflow's logs or history 4. Monitor successful runs and any errors that occur 5. Make adjustments to your workflow as needed based on execution results > πŸ’‘ Regular monitoring helps ensure your integration triggers are functioning correctly and responding to events as expected. ### Understanding Integration Execution 1. Integration triggers run in the Lleverage backend system 2. When published and activated, they listen for events from the external system 3. When an event is detected, the workflow automatically executes 4. No user interface is presented during execution 5. Results are processed according to your workflow configuration > πŸ’‘ Since integration triggers run in the background, it's important to include appropriate notification actions if you need to be alerted when they execute. ### Working with Integration Trigger Data 1. Integration triggers receive data from external systems when events occur 2. This data is made available to subsequent nodes in your workflow 3. Use the @ method or {{ }} method to reference integration data in your workflow 4. Test your workflow with mock data to understand the data structure 5. Build your workflow logic to process this data appropriately > ⚠️ The data structure from integration triggers depends on the specific external system and event type. Always test with sample data first to understand what's available. ### Best Practices for Managing Integration Triggers 1. Regularly check active integrations to ensure they're still needed 2. Deactivate integrations when they're not in use to save on workflow runs 3. Use descriptive names for integration trigger workflows for easy management 4. Monitor execution logs to catch and address any recurring errors 5. Update authentication credentials proactively to prevent disruptions > πŸ’‘ For more efficient management, group related integration triggers in the same project to maintain oversight of interconnected systems. # Scheduling Workflows Scheduled Workflows in Lleverage run automatically at predetermined times or intervals. These workflows are ideal for recurring tasks that need to be performed regularly without manual intervention, such as daily reports, periodic data processing, or routine system checks.

Schedule Publish Panel

### Key Features * Automatic execution based on defined schedules * Background processing without user interaction * Schedule information displayed in the Publish Panel * Ability to toggle schedules on and off * Log tracking for monitoring execution results ### How to View Schedule Information 1. After publishing a workflow with a Schedule trigger 2. The Publish Panel will display schedule information 3. This information shows when your workflow is set to run 4. The schedule format typically shows frequency (hourly, daily, weekly, etc.) 5. It may also include the next scheduled run time > πŸ’‘ Schedule information helps you track when your automated workflows will execute. ### How to Activate and Deactivate Scheduled Workflows 1. After your workflow with a Schedule trigger is configured 2. Click the "Publish" button in the top right corner 3. The Publish Panel will open, showing the activation toggle 4. Toggle the switch ON to activate your scheduled workflow 5. Toggle the switch OFF to temporarily pause the schedule 6. The activation status is also visible in the top bar of the editor > ⚠️ When active, scheduled workflows will run automatically at the specified times, which may consume workflow runs from your plan. ### How to Monitor Scheduled Workflow Execution 1. Since scheduled workflows run in the background, you won't see direct results in real-time 2. Check your workflow logs regularly to verify successful execution 3. Set up notification actions in your workflow if you need alerts about execution 4. Review any error logs to identify and resolve issues 5. Monitor your workflow run usage to ensure you stay within plan limits > πŸ’‘ Regular monitoring is crucial for scheduled workflows since they execute without user intervention. ### How to Troubleshoot Scheduled Workflows 1. If a scheduled workflow isn't running as expected, check its activation status first 2. Verify the schedule configuration is correct 3. Check for any validation errors in the workflow 4. Review logs for any error messages from previous execution attempts 5. Test the workflow manually using the Run Panel to identify potential issues > ⚠️ Authentication issues with external services can cause scheduled workflows to fail silently. Always check connection status if integrations are involved. ### Best Practices for Scheduled Workflows 1. Use descriptive names for scheduled workflows to easily identify their purpose 2. Include error handling in your workflows to manage unexpected situations 3. Consider adding notification actions to alert you about important results or failures 4. Deactivate scheduled workflows when they're not needed to conserve workflow runs 5. Periodically review all active schedules to ensure they're still serving their purpose > πŸ’‘ For critical scheduled workflows, consider adding redundancy checks or confirmation mechanisms to ensure tasks are completed even if initial attempts fail. # Sharing In Lleverage, sharing workflows requires adding users to your project first. This documentation explains how to manage project members and share access to your workflows with team members in a controlled manner. ### Key Features * Role-based access control for projects * Two permission levels: Project Member and Project Owner * Organization-level user management * Project-specific member management * Access restrictions based on project membership ### How to Access Project Settings 1. Navigate to the platform view by clicking the Lleverage logo in the top left corner 2. Alternatively, hover your cursor to the left edge of the screen in workflow canvas view 3. Look for the project selector at the bottom of the left navigation panel 4. Click the people icon (collaboration icon) next to the project selector 5. The Project Settings panel will open on the right side > πŸ’‘ The project selector is located at the bottom of the left-hand navigation panel and displays your current project name. ### How to View and Edit Project Members 1. In the Project Settings panel, select the "Project Members" tab 2. You'll see a list of all current project members 3. Each member has their role displayed next to their name 4. To change a member's role, click the dropdown next to their name 5. Select either "Project Member" or "Project Owner" 6. To remove a member, click the remove option next to their name > πŸ’‘ Project Members can view workflows, while Project Owners have full access including editing capabilities. ### How to Add Existing Organization Members to a Project 1. In the Project Settings panel under the "Project Members" tab 2. Scroll down to the "Add Project Collaborators" section 3. You'll see a list of all organization members not yet added to the project 4. Select the members you want to add to the project 5. Choose their role (Project Member or Project Owner) 6. Confirm to add them to the project > ⚠️ Users cannot access a workflow until they are added as members of the project, even if they have the workflow URL. ### How to Add New Users to Your Organization 1. Click on your name/profile in the navigation panel 2. Select "Settings" from the dropdown menu 3. Navigate to the "Members" tab 4. Click "Invite Member" 5. Enter their email address 6. Optionally, select project access for the new member 7. Send the invitation > πŸ’‘ You must have appropriate permissions at the organization level to add new members. ### How to Share Workflows with Team Members 1. First, ensure the user is added to your organization 2. Add the user to the specific project containing the workflow 3. Assign them the appropriate role (Member for view access, Owner for edit access) 4. Now they can access the workflow through the platform 5. Alternatively, you can share the published workflow URL with them > ⚠️ Remember that sharing a workflow URL will only work if the recipient is already a member of the project. ### Best Practices for Workflow Sharing 1. Audit project memberships regularly to ensure appropriate access 2. Use Project Member role for users who only need to run workflows 3. Reserve Project Owner role for users who need to edit workflows 4. Remove access promptly when a team member no longer requires it 5. Consider creating separate projects for different teams or departments > πŸ’‘ For quick access to the organization members page from project settings, look for the shortcut link at the bottom of the Project Members tab. # Account Setup Creating and setting up your account in Lleverage is the first step toward building powerful AI workflows. The platform offers multiple sign-in options and a guided onboarding experience to help you get started quickly. ### Key Features * Multiple authentication methods (email code or single sign-on) * Guided onboarding experience with AI assistance * Company and role-based personalization * Automatic organization and project creation * Immediate access to workflow canvas ### How to Sign Up for Lleverage 1. Visit the Lleverage website and click the sign-up or get started button 2. You'll be presented with authentication options: * Enter your email to receive a verification code * Or select single sign-on with Google, Microsoft, or GitHub 3. If using email verification: * Enter your first name, last name, and email address * Click "Send Code" * Check your email inbox (including spam folder) for the verification code * Enter the code to proceed 4. If using single sign-on: * Click the preferred provider button (Google, Microsoft, or GitHub) * Complete the authentication process with the selected provider * You'll bypass the email verification step > πŸ’‘ Single sign-on is the fastest way to create an account and provides additional security benefits. ### How to Complete the Onboarding Process 1. After authenticating, you'll enter the guided setup experience 2. You'll be asked a series of questions to personalize your experience: * What company are you with? * What is your role at the company? * Your full name * Company name * Job title * Company website 3. Answer each question to help Lleverage customize your experience 4. You can click "Skip Setup" in the top right corner if you prefer to skip this process > πŸ’‘ Providing accurate information during setup helps Lleverage tailor the experience to your needs and suggest appropriate workflow templates. ### How to Navigate Your New Account 1. After completing setup (or skipping it), you'll be taken directly to the workflow canvas 2. A default project will be created for you automatically 3. Your organization will be named after your company (if provided during setup) 4. The workflow canvas allows you to start creating workflows immediately 5. You can access your organization and project settings through the navigation panel > ⚠️ By proceeding with account creation, you confirm that you agree to Lleverage's terms and conditions. ### How to Join an Existing Organization 1. If you've been invited to join an existing Lleverage organization: 2. You'll receive an email invitation with a link 3. Click the link in the email to accept the invitation 4. Complete the authentication process (email code or single sign-on) 5. You'll be added directly to the organization and projects you were invited to 6. This bypasses the standard organization creation process > πŸ’‘ When joining via invitation, you'll have immediate access to the projects and workflows shared with you. ### How to Switch Between Organizations 1. If you belong to multiple organizations: 2. Click on your profile in the left navigation panel 3. Select the organization icon at the top of the dropdown menu 4. Choose the organization you want to switch to 5. Your project view will update to show projects within the selected organization > πŸ’‘ Each organization has its own set of projects, workflows, and team members. ### Best Practices for Account Setup 1. Use a business email address for better organization alignment 2. Complete the onboarding questions for a more personalized experience 3. Check your spam folder if you don't receive the verification code promptly 4. Consider using single sign-on for enhanced security and convenience 5. Take time to explore the default project to familiarize yourself with the platform > ⚠️ Be sure to use an email address you have consistent access to, as important notifications and verifications will be sent there. # Enterprise SSO Setup Enterprise single sign-on (SSO) routes sign-in through your organisation's identity provider (IdP), such as Microsoft Entra ID. {% hint style="warning" %} When Lleverage activates SSO for a domain, it applies to **all users with that email domain, including existing users**. Plan the activation with your Lleverage contact and select a few key users to validate sign-in immediately. Lleverage can deactivate the connection again if needed. {% endhint %} ## 1. Plan the Rollout Before setup: * Choose an activation time with your Lleverage contact. * Select key users who represent the domains and access roles you need to test. * Make sure those users are invited to the correct Organisation and Projects. * List the primary domain and any additional domains that should use SSO. * Make sure your IT administrator can configure your IdP. Completing the setup does not change sign-in until Lleverage activates the connection. ## 2. Configure the Connection 1. Sign in to Lleverage as an Organisation Owner. 2. Go to **Organisation Settings β†’ SSO**, or open: `https://app.lleverage.ai/{org-slug}/settings/sso` 3. Enter your primary email domain, such as `acme.com`. 4. Select **Setup Portal** and follow the WorkOS instructions. 5. Send your Lleverage contact the primary domain and every additional domain that should use SSO. 6. Agree when Lleverage should activate the connection. {% hint style="info" %} Always open the Setup Portal from the SSO Settings page. Links shared by email are temporary and can expire. {% endhint %} ## 3. Whitelist Users for App Access Some identity providers only let users open an application after they are explicitly assigned to it. Microsoft Entra ID (Azure AD) commonly does this: if the enterprise application requires user assignment, or a Conditional Access policy is scoped to it, unassigned users are blocked at sign-in even though SSO is configured correctly. To avoid a disruptive activation, whitelist your users **before** the connection goes live: 1. In Lleverage, go to **Organisation Settings β†’ SSO**. 2. In the **User Export** card, select **Export CSV** to download all organisation users and their roles. 3. In your IdP, assign (whitelist) those users to the Lleverage application, or add them to the group your access policy targets. 4. Confirm that any Conditional Access policies allow the Lleverage application for those users. Once your users are whitelisted, tell your Lleverage contact that you are ready. They will put the connection live. ## 4. Activate and Validate Once Lleverage activates the connection, all users with a configured domain will use SSO, including existing users. Validate immediately with your selected users: 1. Log out of Lleverage or open a private browser window. 2. Enter the company email address in the regular email login flow. Do **not** select the Microsoft sign-in button. 3. Confirm that the user is redirected to your IdP. 4. Complete sign-in and confirm access to the expected Organisation and Projects. 5. Test at least one invited user from each configured domain. If validation fails, contact Lleverage. The connection can be corrected or deactivated. ## Access Requirements SSO changes authentication only. It does not automatically grant access or provision users. * Invite each user to the Organisation and relevant Projects. * Assign the appropriate roles before testing. * A user without an invitation cannot access the Organisation, even if their domain uses SSO. * Group-based access and SCIM provisioning are not currently supported. See [Roles and Permissions](/roles-and-permissions) for access management. ## Common Issues | Issue | Action | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | The Setup Portal link expired | Open **Organisation Settings β†’ SSO** and select **Setup Portal** again. | | A user is not redirected to the IdP | Use the regular email login flow and ask Lleverage to confirm that the domain is active. | | One domain does not work | Ask Lleverage to confirm that the domain is included in the connection. | | Sign-in works but access is missing | Confirm that the user was invited to the Organisation and relevant Projects. | | All users blocked after activation | Confirm that your users are assigned (whitelisted) to the Lleverage application in your IdP, and that Conditional Access allows it. | | SSO must be rolled back | Ask Lleverage to deactivate the connection. | # Projects Projects in Lleverage serve as organizational containers that help you manage workflows and insights for your organization. They allow you to group related workflows, manage access permissions, and view analytics specific to each project. ### Key Features * Group related workflows in a logical structure * Project-specific analytics and logs * Role-based access control for team members * Customizable project names and emoji icons * Easy switching between different projects ### How to Create a New Project 1. Click on the project selector in the top navigation 2. Select "New Project" from the dropdown menu 3. Enter a descriptive title for your project 4. Select an emoji icon to visually identify your project 5. Optionally, add team members from your organization 6. Click "Create Project" to finalize > πŸ’‘ Choose project names that clearly indicate the purpose or team the project belongs to, such as "Marketing Automations" or "Customer Support Workflows." ### How to Add Members to a Project 1. Create a new project and add members during creation, OR 2. For existing projects, click the project selector in the top navigation 3. Click the people icon next to the selected project 4. In the Project Settings panel, select the "Project Members" tab 5. Add members from your organization to the project 6. Assign appropriate roles (Project Member or Project Owner) > ⚠️ Users must be members of your organization before they can be added to projects. For more details, see the "Sharing Workflows" documentation page. ### How to Switch Between Projects 1. Click on the project selector in the top navigation 2. View the list of projects you have access to 3. Select the project you want to switch to 4. The interface will update to show workflows and data for the selected project > πŸ’‘ The project selector displays your current project name and icon for easy identification. ### How to Organize Workflows with Projects 1. Create separate projects for different teams, departments, or use cases 2. Keep related workflows together within the same project 3. Use descriptive names for both projects and workflows 4. Consider creating a dedicated project for testing or experimental workflows 5. Review project organization periodically to maintain clarity > πŸ’‘ Well-organized projects make it easier to find workflows and manage access permissions efficiently. ### How to View Project Analytics 1. Select the project you want to analyse 2. Open the project's Activity tab to review runs, or check the project dashboard for at-a-glance metrics 3. Review usage statistics, workflow performance, and other metrics 4. Use these insights to optimise your workflows and resource allocation 5. Analytics are localised to each project for focused reporting > πŸ’‘ Project-specific analytics help you understand usage patterns and identify opportunities for improvement within each area of your organization. ### Customising Project Navigation Each project's sidebar and landing page can be tailored in the project's settings, under the Navigation tab. You can choose a sidebar layout, set where people land, and pin frequently used pages. See [Navigation](/platform/navigation) for details. ### Best Practices for Project Management 1. Create a new project for each distinct use case or team 2. Keep the number of workflows per project manageable (consider splitting large projects) 3. Use consistent naming conventions across projects 4. Review and update project member access regularly 5. Maintain documentation about the purpose and contents of each project > ⚠️ Default projects are automatically created for new users, but it's recommended to create purpose-specific projects for better organization. # Subscription Management Leverage offers flexible subscription options to accommodate teams and organizations of all sizes. The platform provides three tiers - Free, Business, and Enterprise - each designed to meet different usage needs and requirements. ### Key Features * Three-tier subscription model (Free, Business, Enterprise) * Secure billing system powered by Stripe * Monthly and annual payment options * Usage monitoring and statistics * Invoice and payment history * Enterprise-level customization options * Analytics dashboard * Custom solution development ### How to Access Subscription Management #### From Organization Settings 1. Navigate to the left-hand platform navigation panel 2. Click on your username at the bottom of the panel 3. Select "Organization Settings" from the dropdown menu 4. Click on the "Billing" tab 5. You'll see your current plan, usage statistics, and available options #### From Workflow Canvas * In the top navigation of any workflow canvas, you'll see a bolt icon that displays your current run usage * Hovering over the bolt icon shows your remaining runs for the current billing period > πŸ’‘ Only organization administrators have access to billing settings and the ability to change subscription plans. ### How to View Current Usage 1. Go to Organization Settings β†’ Billing 2. At the top of the Billing page, you'll see your current usage statistics: * Current period usage (e.g., 26/2500 workflow runs) * Percentage of quota used * Remaining executions * Current billing period dates > πŸ’‘ Monitoring your usage helps you determine if your current plan meets your needs or if you should consider upgrading. #### Usage Limits and Notifications * When you exceed your monthly run limit, the output panel will display a blocking notification * You'll need to wait for the next billing cycle or upgrade your plan to continue * Billing cycles reset monthly - make sure to check back at the start of each month for renewed runs > ⚠️ Once you've used all your runs, workflows will be blocked until the next billing cycle begins or you upgrade your plan. ### Understanding Subscription Tiers #### Free Tier **Start building and testing your AI workflows** * 1 user * 100 workflow runs per month * Access to basic models * 10 MB knowledge base storage * 6 seconds run duration * Shared infrastructure #### Business Tier **For professional teams automating their work** * 5 users * 10,000 monthly workflow runs * Access to all models * 1 GB knowledge base storage * 300 seconds run duration * Dedicated infrastructure with static IP * EU data residency * Priority support * Analytics access #### Enterprise Tier (Custom) **For organizations with advanced needs - like having an AI team embedded in your organization** * Unlimited users * Custom workflow runs * Access to all models * Custom knowledge base storage limits * Custom run duration * Dedicated infrastructure with static IP * Custom integrations * White-glove onboarding for the whole team * Dedicated solution engineers * EU data residency * Custom action development * Advanced analytics > πŸ’‘ For Enterprise-level needs, click "Talk to Sales" to discuss custom options tailored to your organization's requirements. ### Payment Options #### Billing Frequency * **Annual Payment**: Best value with discounted rates * **Monthly Payment**: Available at standard rates > πŸ’‘ Annual payments provide better value and ensure uninterrupted service throughout the year. ### How to Upgrade Your Subscription 1. Go to Organization Settings β†’ Billing 2. Review the available plans displayed on the page 3. Click on the "Upgrade" button for your desired plan 4. Complete the payment details through the secure Stripe integration 5. Your subscription will be immediately upgraded, and the new quota will be available > ⚠️ When upgrading, you'll be charged for the new plan immediately, with prorated amounts for mid-billing cycle changes. ### How to Downgrade Your Subscription 1. Go to Organization Settings β†’ Billing 2. Scroll down to the plan options 3. Locate the "Downgrade" option in the Free plan section 4. Follow the prompts to confirm your downgrade 5. Your plan will change at the end of the current billing cycle > ⚠️ When downgrading, your current plan benefits remain until the end of the billing period, after which the new plan limits will apply. ### How to Manage Payment Methods 1. Navigate to Organization Settings β†’ Billing 2. Find the Payment Methods section 3. View your current payment methods 4. Add new payment methods as needed 5. Update existing payment information 6. Set a default payment method > πŸ’‘ All payment information is securely managed through Stripe, ensuring your data remains protected. ### Custom Solutions and Support #### Need Specific Solutions? If you have specific automation needs or require custom integrations: 1. Book a demo call with our team 2. Discuss your requirements with our solution engineers 3. Get custom action development for your unique workflows 4. Receive tailored onboarding and implementation support #### Analytics and Insights * Access detailed analytics on your workflow performance * Monitor usage patterns and optimization opportunities * Available for Business and Enterprise tiers > πŸ’‘ Contact our sales team to explore custom solutions, action development, and advanced analytics capabilities tailored to your organization's needs # Roles and Permissions Roles in Lleverage define what actions a user can perform at both the **Organisation level** and the **Project level**. This system ensures secure, controlled access to workflows and settings while supporting collaboration across teams. ### Organisation Roles #### Owner (Organisation Admin) * Full control of the Organisation * Can manage all projects, workflows, members, and settings #### Builder * Can create and edit workflows * Can run workflows * Ideal for workflow authors and maintainers #### Operator * Can run workflows only * Cannot modify workflows or settings #### Member * Can view everything in the Organisation * Cannot edit or run workflows ### Project Roles #### Project Admin (formerly Project Owner) * Controls limited to specific projects * Can manage workflows and prompts within the project * Can manage project-specific settings * Can add or remove users from the project * Can modify project connections and secrets #### Project Member * Can view and use workflows within the project * Can contribute to workflows and prompts * Cannot modify project settings * Cannot add or remove users from the project > πŸ’‘ This two-tier permission system allows for both broad Organisation management and granular Project-specific access control. ### How to Manage Organisation Members 1. Click on your name/profile in the navigation panel. 2. Select **Settings** from the dropdown menu. 3. Navigate to the **Members** tab. 4. View all current Organisation members and their roles. 5. To change a member's role, use the role dropdown next to their name. 6. To remove a member, click the remove option. 7. To invite new members, click **Invite Member**. > ⚠️ Only Organisation Admins can manage Organisation members. Members cannot invite or remove other users at the Organisation level. ### How to Invite Members to Your Organisation 1. Go to **Organisation Settings β†’ Members**. 2. Click **Invite Member**. 3. Enter the email address of the person you want to invite. 4. Select their role (Admin or Member). 5. Optionally, specify project access for the new member. 6. Send the invitation. > πŸ’‘ Members can sign up using Google, Microsoft, or GitHub accounts, or through email with a magic link. ### How SSO Affects Access Enterprise SSO authenticates a user's identity but does not automatically add them to an Organisation or Project. 1. Configure SSO for the Organisation and its approved email domains. 2. Invite each user's exact email address to the Organisation. 3. Add the user to the Projects they need. 4. Assign the appropriate Organisation and Project roles. 5. Ask the user to sign in through the regular email login flow. > ⚠️ A matching SSO domain is not an invitation. A user who authenticates without an Organisation invitation cannot access the Organisation and may be sent through the new Organisation flow. For setup instructions, multi-domain configuration and testing, see [Set Up Enterprise SSO](/settings/sso-setup). ### How to Add Members to a Project 1. In **Project Settings**, open the **Project Members** tab. 2. Scroll to the **Add Project Collaborators** section. 3. View all Organisation members not yet added to the project. 4. Select the members you want to add. 5. Choose their role (Project Member or Project Admin). 6. Confirm to add them to the project. > ⚠️ Users cannot access a workflow until they are added as members of the project, even if they have the workflow URL. ### How to Share Workflows with Team Members 1. Ensure the user is added to your Organisation. 2. Add the user to the specific project containing the workflow. 3. Assign them the appropriate role (Member for view access, Admin for management access). 4. They can now access the workflow through the platform. 5. Alternatively, share the published workflow URL with them. > ⚠️ Sharing a workflow URL will only work if the recipient is already a member of the project. ### How to Manage Account Settings 1. Click on your name/profile in the navigation panel. 2. Select **Settings** from the dropdown menu. 3. Navigate through the available tabs: * **Profile**: Update your name, profile picture, and contact information * **Login**: Manage your email and SSO settings * **Organisations**: View and manage the Organisations you belong to * **Projects**: View all projects you have access to across Organisations 4. Make the desired changes and save your settings. > πŸ’‘ Keeping your profile information up to date helps team members identify you in collaborative environments. ### Best Practices for Permission Management * Follow the principle of least privilege: give users only the access they need. * Use Organisation Admin roles sparingly, reserving them for trusted team leaders. * Create project-specific roles for most team members to contain access. * Regularly audit Organisation and project memberships. * Remove access promptly when a team member changes roles or leaves. * Consider creating separate projects for different teams or departments. * For SSO customers, verify that users have both Organisation and Project invitations before testing access. > ⚠️ Regularly review access permissions, especially for projects containing sensitive workflows or data, to maintain security and compliance. # Models Lleverage provides a curated selection of state-of-the-art AI models from leading providers. These models are carefully selected to ensure reliability, security, and optimal performance for various use cases. ### Key Features * Curated selection of best-in-class AI models * Models from leading providers (OpenAI, Anthropic, Google, Together AI, Mistral) * Configurable model settings for fine-tuning outputs * AI-powered model selection recommendations * Custom configurations for different workflow needs * Secure API key management ### How to Choose the Right Model 1. Consider your workflow's specific requirements 2. Use the Lleverage Model Advisor for recommendations based on your use case 3. For simple tasks requiring speed, select faster models like GPT-4.1-nano or Gemini 2.5 Flash 4. For complex reasoning tasks, select more powerful models like GPT-4.1 or Claude 3.7 Sonnet 5. For a balance of performance and cost, consider models like Llama 4 Scout or Mistral Large 2 > πŸ’‘ The Lleverage Model Advisor analyzes your prompt and workflow to recommend the optimal model for your specific use case. ### How to Configure Model Settings 1. Access model configuration in your workflow 2. Select your preferred model provider and specific model 3. Adjust the following parameters as needed: * Max Tokens: Controls response length (-1 for dynamic calculation) * Temperature: Controls creativity and randomness * Top-P (Nucleus): Manages probability threshold for token selection * Frequency Penalty: Reduces repetition in generated text * Presence Penalty: Enhances variety in responses * Stop Sequences: Defines when the model should stop generating > πŸ’‘ For beginners, use the AI helper feature to automatically configure these settings based on your prompt. ### How to Understand Temperature Settings 1. Low temperature (close to 0): * More deterministic, predictable responses * Better for factual tasks, document analysis, data extraction * More focused and coherent outputs * Less creative variety 2. High temperature (close to 1): * More creative, diverse responses * Better for brainstorming, creative writing, idea generation * More varied and potentially surprising outputs * Higher risk of tangential or less relevant content > ⚠️ Higher temperature settings can produce more creative outputs but may occasionally generate less coherent or relevant responses. ### How to Add API Keys to Models 1. Navigate to Connections β†’ Models in your Lleverage account 2. Select the model provider you wish to configure 3. Enter your API key from the corresponding provider 4. Save your changes 5. Your workflows can now use these models with your credentials > ⚠️ Keep your API keys secure and never share them. Lleverage safely stores these keys for your workflows. ### Available Model Providers and Models #### OpenAI * GPT-4.1 * GPT-4.1-mini * GPT-4.1-nano * GPT-o4-mini #### Anthropic * Claude 3.7 Sonnet #### Google * Gemini 2.5 Pro * Gemini 2.5 Flash * Gemini 2.0 Flash #### Together AI * Llama 4 Maverick * Llama 4 Scout * DeepSeek V3 * DeepSeek R1 #### Mistral * Mistral Large 2 > πŸ’‘ This list represents the most current models available on Lleverage. Older models remain accessible but are delisted from the primary selection. ### Best Practices for Model Selection 1. Test multiple models on your specific use case to compare performance 2. Consider the balance between model capability and execution speed 3. Start with the Model Advisor recommendation and fine-tune from there 4. Use more powerful models for complex reasoning, summarization, or creative tasks 5. Use faster models for simple tasks, quick responses, or high-volume workflows 6. Create and save multiple model configurations for different workflow types > πŸ’‘ Lleverage continuously updates its model offerings to ensure you have access to the most reliable and effective AI models available. # Security & Performance At Lleverage, security and performance are core priorities. The platform is built with enterprise-grade security measures while maintaining optimal performance for all workflows, ensuring that your data and automations are both protected and efficient. ### Key Features * SOC 2 Type 2 certification * GDPR compliance * ISO 27001 certification * Secure authentication options * API token management * End-to-end encryption * Optimized workflow performance * Admin support for security issues ### How to Secure Your Lleverage Account 1. Use strong, unique passwords for your Lleverage account 2. Enable single sign-on (SSO) with Google, Microsoft, or GitHub for enhanced security 3. Regularly review active sessions and log out from unused devices 4. Keep your email address up to date to receive security notifications 5. Review and update access permissions for team members regularly > πŸ’‘ Single sign-on (SSO) not only provides convenience but also enhances security through the provider's additional protection measures. ### How to Manage API Tokens Securely 1. Navigate to Organization Settings β†’ Secrets and Variables 2. Create and manage API tokens for external service connections 3. Use the Lleverage AI token to securely access multiple services 4. Never share API tokens or include them directly in workflow code 5. Rotate API tokens periodically following security best practices > ⚠️ API tokens provide access to external services. Always store them securely using Lleverage's built-in secret management rather than hardcoding them in workflows. ### How to Control Access Permissions 1. Follow the principle of least privilege when assigning roles 2. Use Organization Admin roles sparingly, only for trusted team leaders 3. Assign Project Member roles for most users to limit access to specific projects 4. Regularly audit Organization and Project memberships 5. Promptly remove access when team members leave or change roles > πŸ’‘ Regular access audits help ensure that only authorized personnel have access to sensitive workflows and data. ### How to Optimize Workflow Performance 1. Keep workflows focused and efficient by minimizing unnecessary steps 2. Use the appropriate AI models for your specific use case 3. Optimize prompts to generate more precise responses 4. Implement caching for repetitive operations where possible 5. Monitor workflow execution time and resource usage > πŸ’‘ More efficient workflows not only perform better but also consume fewer workflow runs from your subscription quota. ### Understanding Lleverage's Security Compliance 1. **SOC 2 Type 2 Certification**: Validates that Lleverage has established and follows strict information security policies and procedures 2. **GDPR Compliance**: Ensures that European data protection requirements are met 3. **ISO 27001 Certification**: Confirms adherence to international standards for information security management 4. **Enterprise-Grade End-to-End Security**: Protects data in transit and at rest > πŸ’‘ These certifications demonstrate Lleverage's commitment to maintaining the highest security standards for your data and workflows. ### How to Get Security Support 1. For any security concerns or issues, contact admin support immediately 2. Use the support chat in the bottom right corner of the platform 3. Report potential security vulnerabilities promptly 4. Request security documentation if needed for your organization's compliance 5. Reach out for guidance on implementing best security practices for your workflows > ⚠️ If you suspect any security breach or unusual account activity, contact support immediately and consider changing your password. # Secrets and Global Variables Secrets and global variables in Leverage allow you to securely store and reuse sensitive or configuration information across workflows. These live in **Organisation and Project Settings**, not on the workflow canvas. ### Key Features * Secure storage for sensitive information * Organisation-wide and project-specific scope * Easy referencing in workflows * Masked values for secrets * Reusable variable-style usage * Shared safely with teams ### Types of Variables in Leverage #### 1. Secrets (Settings Area) * For sensitive data like API keys, tokens, passwords * Values are masked and hidden after creation * Shared securely with team members * Best for authentication credentials #### 2. Global Variables (Settings Area) * For non-sensitive configuration values * Can be viewed and edited by authorised users * Ideal for URLs, IDs, and config values used across projects * Easier to manage than hard-coding #### 3. Workflow Variables (Canvas Area) * For passing data between actions in a workflow * Created and managed directly in the canvas * Not masked, used only within the workflow context ### Where to Store Secrets and Globals #### Organisation-Level Best for: * API keys used across multiple projects * Company-wide authentication tokens * Shared default config values #### Project-Level Best for: * Project-specific API keys * Environment-based configs (test vs prod) * Limited access credentials > πŸ’‘ Use organisation-level for company-wide resources. Use project-level for specific workflow or environment needs. ### How to Create Organisation Secrets or Variables 1. Click your profile (bottom left) 2. Select **Organisation Settings** 3. In the sidebar, choose **Secrets** or **Global Variables** 4. Click **Add** 5. Enter a name and value 6. Save > ⚠️ Secret values cannot be viewed again after saving. Store the original securely elsewhere. ### How to Create Project Secrets or Variables 1. Navigate to your project 2. Go to **Project Settings** β†’ **Secrets** or **Global Variables** 3. Click **Add** 4. Enter name and value 5. Save > πŸ’‘ Project values override organisation values with the same name. ### How to Use in Workflows Use the `{{env.NAME}}` syntax: **API Calls** ```http Authorization: Bearer {{env.OPENAI_API_KEY}} ``` **Code Blocks** ```javascript const token = "{{env.API_TOKEN}}"; ``` **SQL Queries** ```sql SELECT * FROM users WHERE api_key = '{{env.DATABASE_KEY}}' ``` ### Common Use Cases #### API Integration * Store third-party keys (OpenAI, Slack, DB credentials) #### Team Collaboration * One team member adds the key, others can use it without seeing it #### Environment Management * Separate dev and prod keys, easy switching > πŸ’‘ Use workflow variables for passing data, not for secrets. ### Security Best Practices #### Do * Use clear names (eg `PROD_DB_PASSWORD`) * Rotate keys regularly * Use project-level for limited access #### Don’t * Share secrets outside the platform * Store non-sensitive values as secrets * Forget to update workflows when rotating > ⚠️ Anyone with settings access can overwrite or delete values. Control permissions carefully. ### Managing Existing Values #### Updating 1. Go to Organisation/Project Settings β†’ Secrets/Globals 2. Edit and enter new value #### Deleting 1. Select the item β†’ **Delete** β†’ Confirm > ⚠️ Deleting will break workflows using it. Update workflows before deletion. ### Troubleshooting #### Secret or Global Variable Not Working * Check spelling in `{{env.NAME}}` * Confirm correct level (Organisation vs Project) * Ensure variable exists in the right settings area * Make sure you have admin rights ### Future Improvements We’re improving the secrets and global variables experience with: * Better workflow canvas integration * Easier selection # Logging and Monitoring Lleverage provides logging capabilities to help you debug and understand how your workflows execute. While we're building out comprehensive analytics and monitoring features, you can currently access basic input/output logs for individual nodes. ### Current Logging Features #### Node-Level Input/Output Logs After running a workflow or individual node, you can view the technical logs showing what data was passed into and generated by each node. **How to Access Node Logs:** 1. Run your workflow by clicking the main run button, or run an individual node by clicking the play button on the node itself 2. Once execution completes, a bar will appear below the node 3. Click the "Input" or "Output" tab buttons on this bar 4. The input/output data will expand below the node for review ⚠️ **Note:** These logs are technical in nature and primarily intended for debugging purposes. They show the raw data flowing through your nodes but don't yet provide usage analytics or performance metrics. #### What You Can See * **Input tab**: Shows the exact data that was passed into the node during execution * **Output tab**: Displays what the node generated after processing the input * **Execution indicator**: Visual confirmation that the node has been run πŸ’‘ These logs are automatically generated whenever you run a workflow or individual node - no additional setup required. ### Coming Soon We're actively developing a comprehensive analytics and insights dashboard that will provide: #### Workflow Analytics Dashboard * Organisation and project-level views of all workflow executions * Detailed performance metrics and execution times * Usage patterns and frequency analytics * Resource consumption tracking * System health and uptime monitoring #### Enhanced Run Panel * Full visibility into what was executed and how * Complete execution history * Detailed error tracking and debugging information * Performance optimisation recommendations #### Future Monitoring Capabilities * Visual execution path tracking * Model performance metrics (accuracy, response time, efficiency) * User feedback and error rate analysis * Advanced troubleshooting tools with specific failure point identification * Historical comparisons across workflow versions ⚠️ The logging and monitoring system is under active development. The features described in the "Coming Soon" section will be rolled out progressively to enhance your workflow debugging and optimisation capabilities. # Device Support & Compatibility Lleverage works across multiple devices to give you flexibility in how and where you build your workflows. We recommend desktop for the best experience. Full mobile support is coming very soon! ### Supported Devices #### What We Support * **Desktop computers** (Windows, Mac, Linux) , Recommended * **Tablets** (iPad, Android tablets, Surface) * **Mobile devices** , Enhanced experience coming very soon! > πŸ’‘ **Tip**: We recommend using desktop for the best workflow building experience. ### Browser Compatibility #### Supported Browsers Lleverage works great on all major modern browsers: * **Google Chrome** (recommended) * **Mozilla Firefox** * **Safari** * **Microsoft Edge** * **Opera** > πŸ’‘ **Performance Tip**: Keep your browser updated to the latest version for the best experience. ### System Requirements #### Internet Connection * A stable internet connection for smooth performance * Recommended speed: 10 Mbps or higher * Reliable connectivity ensures AI features work seamlessly ### Need Help? #### Get Support If you experience any issues or have questions about device compatibility, our live support team is here to help! Simply click the chat widget in the bottom right corner of the platform. Our support team is: * Available to assist with any device, related questions * Ready to help optimise your experience * Happy to provide personalised guidance Don't hesitate to reach out , we're here to ensure you have the best possible experience with Lleverage, no matter which device you're using! # Useful Use Cases of Lleverage AI These ready-to-use prompts help you get started with common back-office workflows. Each specifies a trigger and output. Customize them for your ERP and business processes. #### Order Processing When an email arrives with a purchase order PDF, extract the order lines and create a sales order in Business Central. When a new sales order is created in Exact Online, check inventory levels and flag items below safety stock. Start from a form where I paste order details, then validate pricing against our customer price agreements and output exceptions. When an order confirmation email arrives, match it against open purchase orders and update delivery dates in the ERP. On a schedule every morning, export all orders with delivery dates this week and send a production planning summary to the team. When a customer sends an order via EDI, transform it to our internal format and create the order in SAP. Start from chat where I paste a customer email, then extract the order request and draft a confirmation with lead times. When an order ships, pull the tracking number from the carrier portal and send a shipment notification to the customer. #### Invoice Processing When an invoice PDF arrives via email, extract supplier, amounts, and line items, then match against open purchase orders. Start from a form where I upload an invoice, then validate VAT numbers and flag any compliance issues. On a schedule every day at 6pm, export all invoices pending approval and send a summary to the finance team. When a three-way match succeeds (PO, receipt, invoice), automatically approve the invoice for payment in Business Central. When an invoice has missing or incorrect details, draft a clarification email to the supplier with specific questions. Start from chat where I describe a payment discrepancy, then pull the related invoices and receipts for review. When a credit note arrives, match it against the original invoice and update the ledger accordingly. On a schedule every Monday, generate an aging report of unpaid invoices and highlight overdue items. #### Quote Generation Start from a form where I enter product codes and quantities, then generate a quote with current pricing and lead times. When an RFQ email arrives, extract the requirements and draft a response with pricing from our product catalog. Start from chat where I describe a customer request, then calculate pricing based on volume tiers and output a quote PDF. When a quote is approved in the CRM, automatically convert it to a sales order in NetSuite. On a schedule, review quotes older than 14 days and draft follow-up emails for the sales team. When a customer requests a price for a custom configuration, pull BOM costs and calculate a margin-based quote. Start from a form with customer name and products, then check their payment history before generating credit terms. #### Logistics & Shipping When a shipment is booked, generate the CMR document with all required fields pre-filled. On a schedule every afternoon, consolidate today's orders by delivery region and create optimised pick lists. When a carrier sends a delivery exception alert, update the order status and notify the customer. Start from a form where I enter container details, then calculate landed costs including duties and freight. When goods are received, match against the PO, flag quantity discrepancies, and create the goods receipt in the ERP. *** πŸ’‘ These are starting points. Replace the apps and ERPs with your own systems - we integrate with Business Central, Exact, SAP, NetSuite, and more. --- [Next Page](/llms-full.txt/1)