Element events let you decide what happens when someone clicks on things like buttons. This makes the user experience lively and responsive.
Here, we’ll look at how to make buttons interactive in an application. By connecting button clicks to certain actions, you make the user experience better and guide the way the application works.
Events are triggers within your application that respond to user interactions, like clicking a button, logging in, or submitting a form. They bridge the gap between user input and actions on the application’s data.
You can create an action on click or after login.
Here’s an overview of the actions:
You can reorganize the events using the drag-and-drop handle.
Notifications are key for user feedback in your application.
The “Show notification” feature in Application Builder lets you make short messages that pop up on the screen. They tell users about what’s happening in your application and then disappear quickly. This way, users get updates without any mess on the screen.
For example, when someone sends a form, they can’t see what happens next. They might wonder if it worked. That’s where “Show notification” comes in. It gives them a clear message like “Form submitted successfully!” or “Thank you for your inquiry!” to let them know everything was successful.
When a user clicks the button, it directs them to another page.
This feature is perfect for when you want users to go to a certain page after logging in or on click. It could be a confirmation page, a thank you page, or a page with more information.
This improves user flow by directing users to a specific web address. It’s handy for accessing related links.
The HTTP request action allows you to send requests to external APIs and services directly from your application. This powerful feature enables integration with third-party systems, data submission to external endpoints, and triggering of external workflows.
Here’s how it works:
This action is perfect for integrating with payment processors, sending data to CRM systems, triggering automated workflows, or communicating with any external API that your application needs to interact with.
This event lets users submit data that creates a new row in a table. It’s perfect for building forms to collect data, like applications, feedback, or purchase orders.
Here’s how it works:
For example: A job application form creates a new record in a “Job Applications” table with the applicant’s details and the specific job they’re applying for. Whenever an applicant submits the form, a new row will be created in the table, automatically capturing their information.
This event allows users to modify existing data entries within the application. It facilitates the editing process, allowing users to make necessary changes to the data.
For example, if you have a list of tasks, the task page can contain a form through which employees can request task changes.
After the event occurs, the application automatically updates the designated row with the new information, reflecting the user’s requested changes.
You can send custom emails using the Send email action inside your workflow. All you need is access to an SMTP server like Gmail, Outlook, or your company mail.
You will be prompted to set up an SMTP integration to send emails.
Field | Description |
---|---|
SMTP Host | The SMTP server address, e.g., smtp.gmail.com |
SMTP Port | Typically 587 for TLS or 465 for SSL |
Use TLS | Enable if required (✅ recommended for Gmail, Outlook, etc.) |
Username | Your full email address |
Password | Your email password or an app-specific password (recommended) |
💡 Note for Gmail users: You need to create an App Password and use it here instead of your regular email password.
Once saved, this SMTP integration will be available for all future email actions.
Fill in the email details to customize your message:
Field | Description |
---|---|
To | Recipient’s email address |
Subject | The subject line of your email |
Message | Email body content (supports both plain text and HTML) |
You can also configure additional fields such as CC, BCC, and select the Body Type as needed.
Automate confirmations, alerts, and updates based on user interactions.
Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions—we’re ready to assist you.