From glide
Creates server-side workflows in Glide apps triggered by incoming emails. Sets up email address, configures variables (sender, subject, body, HTML, attachments), names workflow, and adds nodes like support ticket creation.
npx claudepluginhub glideapps/glide-code --plugin glideCreates a server-side workflow triggered when an email is received at a Glide-provided email address. All parts of the email become available as variables. | Variable | Description | Example | |----------|-------------|---------| | **From** | Sender email address | `john@example.com` | | **From Name** | Sender display name | `John Doe` | | **To** | Recipient address (the Glide address) | `abc12...
Send transactional emails, batch emails, manage attachments, schedule and cancel emails using Resend API
Subagent for designing, building, validating, debugging, and optimizing n8n automation workflows, including node discovery and best practices.
Designs complex n8n workflows for automations: architectures with JSON nodes, error handling (retries, notifications), patterns like AI content pipelines/lead qualification/document processing, OpenAI/JS integrations.
Share bugs, ideas, or general feedback.
Creates a server-side workflow triggered when an email is received at a Glide-provided email address. All parts of the email become available as variables.
| Variable | Description | Example |
|---|---|---|
| From | Sender email address | john@example.com |
| From Name | Sender display name | John Doe |
| To | Recipient address (the Glide address) | abc123@workflows.glideapps.com |
| Subject | Email subject line | New Order #12345 |
| Body | Plain text body | Order details... |
| HTML Body | HTML formatted body | <p>Order details...</p> |
| Date | When email was received | Timestamp |
| Attachments | File attachments | URLs to attachments |
| Reply-To | Reply address if different | support@example.com |
| CC | CC recipients | Email addresses |
COMMAND: NAVIGATE
URL: https://go.glideapps.com/app/{appId}/workflows
EXPECTED: Workflow editor loads
COMMAND: SNAPSHOT
PURPOSE: Find new workflow button
COMMAND: CLICK
REF: {ref of new workflow button}
ELEMENT: New workflow button
EXPECTED: Workflow type selection appears
COMMAND: SNAPSHOT
PURPOSE: Find workflow type options
COMMAND: CLICK
REF: {ref of Email option}
ELEMENT: "On Email" or "Email" trigger type
EXPECTED: New email workflow created
VERIFY: Right panel shows email address for receiving
COMMAND: SNAPSHOT
PURPOSE: Find workflow name input
COMMAND: CLICK
REF: {ref of name input}
ELEMENT: Workflow name input
COMMAND: TYPE
REF: {ref of name input}
ELEMENT: Workflow name
TEXT: {workflowName}
EXAMPLES: "Email Lead Capture", "Support Ticket Creator", "Order Parser"
COMMAND: SNAPSHOT
PURPOSE: Find email address in properties panel
FIND:
- Email address displayed in right panel
- Copy button or selectable text
- Usually format: {unique-id}@workflows.glideapps.com
Copy the email address:
COMMAND: CLICK
REF: {ref of copy button or email field}
ELEMENT: Copy email address button
Or select and copy manually.
COMMAND: EVALUATE
CODE: async () => {
try {
const email = await navigator.clipboard.readText();
return { inboundEmail: email };
} catch (err) {
return { error: err.message };
}
}
EXPECTED: JSON with inboundEmail
SAVE: Store this address to provide to user/external system
Now add nodes to process the incoming email.
Common patterns:
When configuring nodes, email variables are available as data sources:
COMMAND: SNAPSHOT
PURPOSE: Find data binding in node configuration
FIND: Data/variable selector in node properties
COMMAND: CLICK
REF: {ref of data selector}
ELEMENT: Data source selector
COMMAND: SNAPSHOT
PURPOSE: Find email variables
FIND: Email trigger variables:
- From
- Subject
- Body
- (all others listed above)
COMMAND: CLICK
REF: {ref of desired variable}
ELEMENT: "{variableName}" email variable
EXPECTED: Node now uses that email data
COMMAND: SNAPSHOT
PURPOSE: Confirm email workflow setup
VERIFY:
- Workflow name is set
- Email address is visible and copied
- Nodes are configured with email variables
Use Query JSON or string parsing:
Example - Email body with key:value pairs:
Order ID: 12345
Customer: John Doe
Total: $99.99
Use Template columns or string operations in Glide to extract.
Consider using AI-powered parsing:
ISSUE: No email address in properties panel
CHECK:
- Is this an Email type workflow?
- Is the workflow saved?
TRY: Refresh page and check again
ISSUE: Sent email but workflow didn't run
CHECK:
- Is the email sent to exact address? (case matters)
- Is the sender's email on a blocklist?
- Did the email get marked as spam?
TRY: Send test email from different sender
ISSUE: Can't access email attachments
CHECK:
- Does the email have attachments?
- Are attachments within size limits?
NOTE: Attachments are provided as URLs, not direct files
EMAIL WORKFLOW CREATED:
Name: {workflowName}
Inbound Email: {email address}
Variables Used: {list of email variables bound in nodes}
Nodes Added: {list}
Status: SUCCESS | FAILED
USER ACTION REQUIRED:
Send emails to: {inbound email address}
Or configure external system to forward to this address.