Connect LFG Alarm to n8n

Before you start

• Get the LFG Alarm app on your phone from Google Play or the App Store, and sign in. n8n makes or triggers the alarms; the app is what rings them.
• n8n with the MCP Client Tool node (it ships with n8n, cloud or self-hosted, and works with the AI Agent node).
• A personal key for the agent route, since an n8n workflow cannot do a sign-in. Make one below.

A key acts as you. Any workflow that holds it sets alarms on your phone, so keep it in an n8n credential, not pasted into a node, and keep it out of workflows that strangers can trigger, such as a public chat or form. There is no LFG Alarm node for n8n yet; this page uses n8n's own nodes.

Make a key

1. In LFG Alarm, open Settings > Connected AI apps, on lfg.gm or in the app.
2. Tap Make a key, name it after the workflow (for example "n8n"), and tap Make the key.
3. The key is shown once, with Copy and Done. Copy it, then tap Done.

Keys start with lfg_pat_, work only at the LFG Alarm MCP server, and allow 60 calls a minute and, each day, up to 50 new alarms, 50 comments and 20 uploads. A key has the same plan limits as signing in.

Ring your phone from a workflow

The shortest path, and no key at all: when a workflow decides something needs a human, it rings an anything alarm.

1. In LFG Alarm, make an Anything alarm and copy its private link.
2. In n8n, add an HTTP Request node where the workflow should ring you. Method: POST. URL: the alarm's link.
3. Run the workflow. Your phone rings, and so do the friends you shared the alarm with.

Good fits: an order over a set amount, a form from a VIP client, a failed backup, a price your own workflow computes. See How to make any app, script or feed ring your phone.

Let an n8n agent set alarms

1. Add an AI Agent node with a chat model.
2. Under the agent's Tool, add MCP Client Tool.
3. Endpoint: https://mcp.lfg.gm. Server Transport: HTTP Streamable (not the deprecated SSE).
4. Authentication: Bearer Auth, and create a credential with your lfg_pat_ key. (Header Auth also works: name Authorization, value Bearer lfg_pat_....)
5. Tools to Include: Selected is the safe choice for an automation. Pick what the workflow needs, for example set_time_alarm and list_my_alarms, and leave out delete_alarm.
6. In the agent's system message, say when to use it: "When a task needs a person to act at a set time, set an LFG Alarm and report the time it rings."

Try it

Once the MCP Client Tool is attached, send the agent:

More ideas: a schedule trigger that asks the agent each Sunday to set the week's early alarms from a calendar, or a workflow that reads an event email and sets an event alarm from its Luma or Partiful link. Through a key, LFG Alarm can set time, price, post, event, wallet, trader and anything alarms, pick a sound or a look from the library, and add your friends or a whole group once you confirm. See Using LFG Alarm from your AI agent.

If it does not work

• The tool list is empty or the node errors on connect. Check the transport is HTTP Streamable and the endpoint is https://mcp.lfg.gm exactly.
• 401 Unauthorized. The credential must send Bearer and the key. Make a new key if this one was removed.
• Adding friends stalls. LFG Alarm lists who it would add and waits for a yes. A workflow with nobody to answer should set private alarms, or name only people already confirmed.

Learn more

• How to make any app, script or feed ring your phone
• Using LFG Alarm from your AI agent
• Connect LFG Alarm to another AI app

Sources and further reading

• n8n docs: MCP Client Tool node
• n8n docs: HTTP Request node

LFG Alarm is not affiliated with n8n.