How can I trigger an n8n workflow when an MMS (photo-only SMS) is received?

Based on the n8n documentation, there isn’t any native node specifically designed to trigger workflows on receiving an MMS (or SMS with a photo). The documented trigger nodes (like WhatsApp Trigger or Telegram Trigger) cover events within those messaging platforms only.

If your goal is to trigger a workflow when an MMS arrives, the generally recommended approach is to use an external service or gateway that supports SMS/MMS events (for example, third-party providers such as Twilio). These services can forward the incoming MMS data via an HTTP request to an n8n workflow using a Webhook Trigger node.

Here’s a high-level overview of one potential solution:

1. Choose an SMS/MMS Provider:
   Use a service like Twilio that supports receiving MMS messages. These providers typically let you configure a webhook URL to which incoming MMS data is POSTed.

2. Set Up an n8n Webhook Trigger:
   Create an n8n workflow with the Webhook Trigger node. For example, you might configure it like this:

   YAMLCopied
   # An example configuration for the Webhook Trigger node:
   HTTP Method: POST
   Path: /webhook/mms-received

3. Forward Data to n8n:
   In your service (e.g., Twilio), point the incoming MMS webhook URL to your n8n instance (using the public HTTPS address). When an MMS is received, the provider will send the data (including the photo URL or data) to your workflow.

4. Process the Incoming Data:
   In your workflow, add nodes to process the incoming MMS data. You can extract the media URL, download the image if needed, and perform further operations based on your requirements.

If you already have an app (like Tasker with AutoNotification) working to send an HTTP request to n8n, you’re on the right track. The key challenge is reliably obtaining the MMS content and formatting it into a proper HTTP POST for n8n. At that point, the n8n side is covered by its standard Webhook Trigger configuration.

For more details on configuring webhook-based workflows, see the documentation on the Webhook Trigger node. While it doesn’t cover SMS/MMS gateways directly, it explains how incoming HTTP requests are processed by n8n—which is the method you’d use in this scenario.

I hope this helps clarify a potential path forward! If you need more detailed information on any n8n integration or node configuration, feel free to ask.