Google setup
Working with Google Mail in Afina
The Google Mail integration is the central hub of Afina email automation. It is the place where every IMAP connection, app password, mailbox, and message-search rule finds a home. Users get a smooth experience to plug in a Gmail address, set up the IMAP host, configure the port, and run scripts that wait for emails, read content, and pull data through extraction rules. Furthermore, the integration offers reliable management of email addresses, app passwords, server hostnames, ports, and the mailbox data attached to each script.
Once the mailbox is loaded into the system, the "Mail Data" page presents the entire connection on display. The best part is the convenience: a user can monitor each connection status, locate any specific mailbox in seconds with the matching label, and trigger probes across many integrations in a single click.
Benefits of the Gmail Integration
- A wide list of email scenarios is available through the "Email" components for every business need.
- Users can configure each mailbox through proper IMAP host and port fields.
- Downstream automation scenarios easily reach into a message through the connection reference.
- The integration supports both single mailbox links and full multi-mailbox pipelines at any moment.
- Any user can have a smooth experience while building messaging flows with a unique configuration.
Once the credentials are saved, the freshly-built mailbox joins the rest of the entries under "Mail Data". From this point, a user can run scripts against the mailbox, edit related settings, attach the mailbox to a pipeline, mark older accounts for cleanup, link the right credential to a workflow, and send the integration into automation tasks. Thus, every newly-saved mailbox becomes immediately operational.
Creating an App Password
A wide list of reasons exists to use the app password feature in Afina. To start with, it offers brilliant speed for fresh integrations. Then a user can shift focus to the reliability with already-prepared Google credentials. The feature is totally effective for setting up a working environment, deploying a large batch of mailboxes at once, or restoring a known good messaging setup after a system change.
Furthermore, the Google account dashboard at the top of the security section provides uninterrupted access to app password creation. A user picks the mail flavor and points at the new password label. The platform takes care of the rest. Detailed instructions are available here: Google app passwords
Moreover, the app password feature supports a connected two-factor authentication state. So, a user can pull a fresh credential straight from Google whenever the security setup is configured. After the password is generated, the freshly-built credential settles into the local notes and becomes immediately ready for launching, configuration, and use inside scripts.
Adding the Mailbox to Afina
Different mailbox scenarios are available for various business needs. Users can drop a mailbox one at a time, or rotate a stack of accounts whenever the catalog changes. For routine setup, a user fills in the IMAP fields with the matching values: the Gmail address, the app password, imap.gmail.com for the server, and 993 for the port. The bulk option is located inside the "Mail Data" list at the top of the "Mail" section.
Before a mailbox change clicks through, a user should check that the targeted account is no longer wired into an active job, a script, or a workflow that is currently running. The reason is simple: a mailbox change pulls related script references, tasks, message templates, and work history along with the account. Thus, an unintended change may bring extra losses.
On the other hand, full mailbox replacement is not always the right move. Many users prefer to keep an older mailbox around, shift its tag, swap its app password, or switch the connection to a fresh Gmail address. The positive part is that the mailbox simply sits on the bench for a while without any data being permanently lost.
Using Mail in Scripts and Global Variables
Each mailbox in Afina can carry an extensive load of message data. The data is exactly what scripts and automation jobs reach into during execution. Some examples are confirmation codes, verification links, login receipts, password reset emails, system alerts, and any other parameter that should look different from one mailbox to the next.
The best part of this functionality is reusability. One mailbox can be used everywhere with consistent results. Each script plugs in its own value whenever the call reaches the messaging step. Instead of cloning the mailbox per script, a user simply prepares the variables correctly. Thus, automation becomes more flexible.
Furthermore, Afina offers two flavors of credential storage: standard inline values and global variables. Global variables are reserved for sensitive material that should not sit around in plain text. Examples include the email address, the app password, the IMAP host, and the IMAP port stored as __setting__email__, __setting__password__, __setting__imap__host__, and __setting__imap__port__ with their matching ${...} references.
Both kinds of credentials reach scripts through a global-variable construct. The feature is impeccable for keeping a hundred scripts wired to the same mailbox in one shot. It is not limited here. Users can also pair the variable with planned rotation windows, or stash a snapshot before any major change is applied.