Integration Trigger

Integration Trigger

Overview

The Integration Trigger connects your workflows to real-time events from your connected applications. When something happens in Slack, Google Sheets, your CRM, or any other integrated service, your workflow springs into action automatically.

Best for: Responding to events in connected apps, real-time automation, cross-platform workflows, and event-driven processes.

When to Use Integration Trigger

Perfect for:

• New Slack messages in specific channels

• New or updated rows in Google Sheets

• Emails received in specific folders

• Calendar events created or updated

• New files added to folders (Drive, Dropbox, OneDrive)

• CRM record changes (new leads, updated deals)

• Project management updates (new tasks, status changes)

Not ideal for:

• Custom API integrations (use Webhook Trigger)

• Scheduled recurring tasks (use Scheduled Trigger)

• User-submitted forms (use Form Trigger)

Configuration

1

Select Integration

Choose from your workspace’s connected integrations:

• Communication: Slack, Microsoft Teams, Gmail

• Productivity: Google Sheets, Notion, Asana, Jira

• Storage: Google Drive, OneDrive, Dropbox

• CRM: Salesforce, HubSpot

• Calendar: Google Calendar, Outlook Calendar

• And many more…

Integration Trigger

2

Choose Event Type

Each integration offers specific trigger events.

Slack:

• New message in channel

• New direct message

• Message with specific emoji reaction

• User joined channel

Google Sheets:

• New row added

• Row updated

• Row deleted

• Spreadsheet opened

Gmail:

• New email received

• Email in specific folder

• Email with specific label

• Email matching search criteria

Google Calendar:

• Event created

• Event updated

• Event starting soon

• Event canceled

3

Configure Event Filters

Narrow down which events trigger your workflow.

For Slack:

• Specific channels only

• Messages from certain users

• Messages containing keywords

• Messages with attachments

For Google Sheets:

• Specific spreadsheet and sheet

• Rows matching criteria

• Changes to specific columns

For Email:

• From specific senders

• With specific subjects

• To specific addresses

• With attachments

Integration Trigger

4

Connect Account

If not already connected:

• Click “Connect Account”

• Authorize Langdock to access the integration

• Select the specific account (if multiple)

• Grant necessary permissions

Example Use Cases

Slack → Ticket Creation

Integration Trigger (New message in #support channel)
→ Agent: Extract issue details from message
→ Action: Create JIRA ticket
→ Action: Reply in Slack thread with ticket number

Google Sheets → Data Processing

Integration Trigger (New row in "Leads" sheet)
→ HTTP Request: Enrich lead data from external API
→ Agent: Score lead quality
→ Condition: Check score
  → High: Notify sales team
  → Low: Add to nurture campaign
→ Action: Update row with score and status

Gmail → Document Processing

Integration Trigger (New email with attachment)
→ Agent: Extract and summarize document content
→ Action: Save summary to Google Drive
→ Action: Create task in project management tool
→ Action: Reply to email confirming receipt

Calendar → Meeting Prep

Integration Trigger (Event starting in 1 hour)
→ HTTP Request: Fetch meeting context from CRM
→ Agent: Generate meeting brief
→ Action: Send Slack message to attendees
→ Action: Create Google Doc with meeting notes template

Drive → Content Approval

Integration Trigger (New file in "Pending Approval" folder)
→ Agent: Review content against guidelines
→ Condition: Check approval recommendation
  → Approved: Move to "Published" folder
  → Needs Changes: Send feedback to creator
→ Notification: Alert stakeholders of decision

Accessing Integration Data

Use the trigger variable to access event data.

Example: Gmail Event Data

Subject:
{{trigger.output.subject}}
From:
{{trigger.output.from}}
Body:
{{trigger.output.body}}
Has Attachments:
{{trigger.output.has_attachments}}
Labels:
{{trigger.output.labels}}

Testing Integration Triggers

Test Panel

1

Click on the Integration Trigger node

2

Click “Test” in the toolbar

3

View recent events from the integration

4

Select an event to test with

5

Run the workflow with that event’s data

Trigger Real Events

1

Manually create the event in the integration

• Send a Slack message

• Add a row to Google Sheets

• Create a calendar event

2

Wait for the event to trigger (usually within seconds)

3

Check the Runs tab for execution

4

Review the workflow results

Common Integration Patterns

Bidirectional Sync

Integration Trigger (Sheets updated)
→ Code: Transform data
→ HTTP Request: Update external system
→ Condition: Check if update successful
  → Success: Update status in Sheets
  → Failure: Notify admin

Best Practices

• Filter Events Early Use integration filters to only trigger on relevant events. Processing every Slack message is expensive and slow.

• Handle Duplicates Some integrations may send duplicate events. Add logic to detect and skip duplicates using unique IDs.

• Monitor Permissions Integration permissions can expire. Set up alerts for authentication failures.

• Test with Real Events Don’t just use test data — trigger real events in the integration and verify your workflow handles them correctly.

• Add Rate Limiting If an integration event happens frequently (e.g., many Slack messages), consider adding conditions to prevent overwhelming your workflow.

• Preserve Event Data Store original event data early in the workflow in case you need to reference it later.

Next Steps

• Action Node — Perform actions in integrated apps

• Condition Node — Route based on integration data

• Agent Node — Process integration data with AI

• Webhook Trigger — Trigger workflows with custom webhooks

Integration Trigger