Connect FTP to Intercom and automate your tasks

Why integrate FTP with Intercom

The FTP to Intercom integration helps you sync data, automate manual tasks, and keep your stack aligned — without writing code.

Receive inventory updates from your supplier

When a supplier drops a CSV on your FTP server, MESA picks it up on schedule and updates Shopify product inventory automatically. Stock levels stay accurate without manual imports or copy-paste.

Send order files to your fulfillment partner

After orders are placed, MESA generates a formatted CSV and uploads it to your 3PL's FTP server. Your fulfillment partner has what they need without manual exports or email attachments.

Sync product catalog updates from a supplier feed

MESA reads your supplier's product file on a schedule and maps the data to Shopify's format. New SKUs, updated prices, and changed descriptions land in your store without manual intervention.

Give your support team full Shopify context on every conversation

When a customer starts a conversation in Intercom, MESA pulls their Shopify order history, tags, and customer details into the thread. Your team responds with the full picture without switching between tools to find it.

Create and update Shopify customer records from Intercom conversations

When a new contact is created or a key detail is captured in Intercom, MESA writes it to the corresponding Shopify customer record. Your store and your support platform share a single view of every customer without periodic reconciliation.

Trigger Intercom messages from Shopify order and fulfillment events

When an order ships, a delivery is delayed, or a return is filed in Shopify, MESA sends the signal to Intercom and triggers the right message to the customer. Your proactive outreach runs on what actually happens in your store, not on a fixed schedule.

Build any FTP and Intercom automation

MESA helps you connect apps to automate repetitive tasks. A trigger is an event that starts a workflow, and actions are the steps that occur when it's running.

Admin Initiated Message to User

Starts when an admin initiates a message to a user.

• Type
• Conversation ID
• Created At
• Updated At
• Conversation Source
• Conversation Contacts
• Assigned Admin
• Assigned Team
• State
• Priority
• Tags
• Custom Attributes

Contact Archived

Starts when a contact is archived.

• Contact ID
• Object Type
• Archived
• Archived At

Contact Deleted

Starts when a contact is deleted.

• Contact ID
• Object Type
• Deleted
• Deleted At
• Workspace ID
• External ID
• Email Address
• Name

Contact Email Updated

Starts when a contact's email is updated.

• Type
• Contact ID
• Workspace ID
• External ID
• Role
• Email Address
• Phone Number
• Name
• Avatar
• Owner
• Created At
• Updated At
• Signed Up At
• Last Seen At
• Location
• Custom Attributes
• Tags

Contact User Created

Starts when a contact user is created.

Contact User Updated

Starts when a contact user is updated.

Interaction Events

You can also handle various interaction events like:

• Conversation Closed
• Conversation Opened
• Conversation Read
• Message Received from User or Lead
• Note Added to Conversation
• Reply Received from User or Lead

Fetch and Update Files via FTP

• Fetch CSV File: Fetch a CSV file that matches a pattern from an FTP server.
• Fetch XML File: Fetch a XML file that matches a pattern from an FTP server.
• Save FTP File: Save a file to an FTP server.

Conclusion

MESA includes hands-on support from automation experts who know how to get things done. Enjoy a 7-day free trial. Get your first workflow in minutes.