Glide + Customer.io: Supported Email Triggers & Variables

Last updated: March 16, 2026

What This Guide Is For

Your members expect to hear from you at the right moment — when their application is approved, when their account is funded, when someone they invited completes their profile. Those moments build trust. Miss them, and you miss the chance to make a member feel taken care of.

This guide gives your team a complete picture of every automated email your institution can send today. No technical knowledge required — just a clear, organized reference for what's available, what kicks each email off, and what member details you can use to make every message feel like it was written specifically for them.

The more intentionally you set these up, the better your member experience gets. Start here.

Overview

There are two types of emails that you can set up in Customer.io:

Transactional emails send immediately when one specific thing happens, like an approval or a denial.
Campaign emails are part of a larger automated journey with timing, branching, and multiple steps — like a 3-part onboarding series that starts the moment a member is approved.

The guide below shows the data available to use in an email as well as the supported transactional and campaign belows.

Customer Information Available in Any Email

These are details we already have on file that can be pulled into any email template automatically. You can open an email with the member's first name or reference their member number, without anyone having to type it manually.

Standard Customer Details

Field Name	What It Contains	Identifier
First name	Member's first name	`first_name`
Last name	Member's last name	`last_name`
Email	Member's email address	`email`
Phone number	Member's phone number	`phone`
Phone country code	Country code for their phone number	`country_code`
Member number	Their number in your core banking system	`external_core_id`

Invite-Related Details

When a member is being invited to join an account as a joint owner, beneficiary, or sponsor, emails can reference who sent the invitation — making the message feel warm and familiar rather than generic.

Field	What It Contains	Identifier
Inviter's first name	First name of the person who sent the invite	inviter_first_name
Inviter's last name	Last name of the person who sent the invite	inviter_last_name

How to use customer information within emails

Within the template editor, reference a supported field from above by using curly brackets and the identifier in the format below:

{{customer.identifer | default:’text’}}

"Identifier" = the identifier variable from the table above

"text" = the default value if the variable is not available for any reason

For example if you are trying to specify the customer's name, use {{customer.first_name | default:’member’}}

Transactional Emails

These are single, immediate emails — each one fires automatically the moment a specific event happens. Where noted, the email can include extra details specific to that event, like a dollar amount or a personalized link. These are only passed in for the email specified.

Application Status

Email	When It Sends	Extra Details Available
Application Pending	When a member submits their application	None
Welcome	When their application is approved	None
Application Denied	When their application is rejected	None
Application Automatically Closed	When an application is closed due to inactivity	None

ChexSystems Denials

Sent when a member's application is declined due to a ChexSystems screening. There are two versions depending on where in the process the denial occurs. Both emails can include the application type, application ID, report date, ChexSystems score, reason codes, and score date.

Email

When It Sends

Extra Details Available

Application Denial (ChexSystems)

When a denial occurs at the member or membership level

Application type - e.g. Personal Membership (app_type)
Application ID - e.g. Glide app ID (application_id)
Report date (generation_date)
ChexSystems score (qualifile_score)
reason codes (reason_codes)
Score date (score_date)

Share Denial (ChexSystems)

When a denial occurs at the share level

Application type - e.g. Personal Membership (app_type)
Application ID - e.g. Glide app ID (application_id)
Report date (generation_date)
ChexSystems score (qualifile_score)
reason codes (reason_codes)
Score date (score_date)

Account Approvals

Email

When It Sends

Extra Details Available

Checking Account Approved

When a checking account is approved

None

Share Certificate Approved

When a certificate (CD) account is approved

None

Funding

Email	When It Sends	Extra Details Available
Funding Initiated	When ACH or card funding is started	Transfer amount (`transfer_amount`), last 4 digits (`funding_last_4`), funding type e.g. card/ach (`funding_name`)

Debit Card and Courtesy Pay

Email	When It Sends	Extra Details Available
Debit Card Requested	When a member requests a debit card	None

Identity Verification

Email	When It Sends	Extra Details Available
Request Identity Verification	When a member needs to retry ID verification	A direct link for the member to complete verification (`plaid_link`)

Microdeposits

Only set up if your FI is accepting microdeposits as a verification method on our onboarding page.

Email	When It Sends	Extra Details Available
Microdeposit Instructions Sent	When verification instructions are delivered to the member	None
Microdeposit Failed	When microdeposit verification fails	None

Roles and Invitations

These emails handle inviting someone to share an account and keeping all parties informed throughout that process.

Email	Sent To	When It Sends	Extra Details Available
Role Invitation	The person being invited	When a joint owner, beneficiary, or sponsor is invited	Role name (`role_name`), inviter's name (`inviter_first_name, inviter_last_name`), invitation link (`invite_link`), list of shares (`shares_list`).
Disclosure Invitation	The person being invited	When a document signature link is sent	Invitation link (`invite_link`), primary signer's name (`primary_signer_first_name`), inviter's name (`inviter_first_name, inviter_last_name`), role name (`role_name`)
Role Added	The primary member	When an invited person completes their flow	Role name (`role_name`), invitee's first and last name (`invitee_first_name`, `invitee_last_name`)
Joint Added to Shares	The joint owner	When a share-level role is added to shares	Primary member's name (primary_name) joint owner's name (joint_name), list of shares (shares_list)
Role Automatically Closed	The primary member	When an invitation expires or is auto-closed	None
Share Automatically Closed	The primary member	When a share is auto-closed	None

Loans [DLA-only]

Email	When It Sends	Extra Details Available
Loan Application Submitted	When a loan application is received	None
Loan Application Approved	When a loan is approved	None
Loan Application Denied	When a loan is denied	None

How to use variables within transactional emails:

Within the template editor, reference a supported field from above by using curly brackets and the identifier in the format below:

{{customer.identifer | default:’text’}}

"Identifier" = the identifier variable from the table above

"text" = the default value if the variable is not available for any reason

For example if you are trying to specify the customer's name, use {{customer.first_name | default:’member’}}

Campaign Emails

Where transactional emails handle single moments, campaign emails handle the bigger picture. They let you build sequences — a welcome series, an onboarding journey, a follow-up flow — that unfold over time and adapt based on what the member has done.

Glide supports the following campaigns:

Personal (Applies to personal, minor, and trust applications):
- Onboarding Campaign
- Incomplete Applications
- Joint Owner/Beneficiary Invites
Business:
- Business Onboarding Campaign
- Incomplete Business Application
- Business Role Invite

While setting up campaigns within CIO, you'll be able to use the following events to trigger when campaign should start. The list of events below can be used as conditions to emails as well in a campaign.

Application Events

Event	When It Occurs	Extra Info Available
Application Created	Member starts an application	None
Application Submitted	Member submits their application	None
Application Approved	Credit union approves the application	Whether the member has a checking account (yes or no)
Application Rejected	Application is rejected	None
Application Closed	Application is closed manually or automatically	None

Example: When a member is approved, automatically send a different onboarding series depending on whether they opened a checking account — so every email they receive is relevant to the products they actually have.

Role and Invitation Events

Event	When It Occurs	Extra Info Available
Role Invited	A joint owner, beneficiary, or sponsor is invited	Role name
Role Invitation Complete	The invited person finishes their flow	Role name, inviter's first and last name

Account and Card Events

Event	When It Occurs	Extra Info Available
Checking Account Created	A new checking account is opened	Account type, product name
Debit Card Requested	Member requests a debit card	Card type, delivery method
Card Payment Email Sent	A card payment notification fires	Payment amount, last 4 digits of card

Transfer and Deposit Events

Event	When It Occurs	Extra Info Available
Transfer Initiated	A fund transfer is started	Transfer amount, transfer type, from account, to account
Direct Deposit Completed	Member sets up direct deposit	Employer name, deposit amount

Online Banking Events

Event	When It Occurs	Extra Info Available
Online Banking Accessed	Member logs into online banking for the first time	None

Loan Events [DLA-only]

Event	When It Occurs	Extra Info Available
Loan Application Created	Member starts a loan application	Loan type
Loan Application Submitted	Loan application is submitted for review	Loan type, loan amount

Business and Trust Events

Event	When It Occurs	Extra Info Available
Business Application Submitted	A business account application is submitted	Business name
Business Application Approved	A business account application is approved	Business name, whether it has a checking account (yes or no)
Trust Application Started	A trust account application is started	Trust type, trust name

Questions or Issues?

If an email isn't sending or something doesn't look right, contact your implementation partner with the member's email address, the name of the email or campaign, and when the issue occurred.