---
title: "IFTTT"
description: "Use Rumoro mentions in IFTTT Applets, and let Applets manage keywords and triage mentions."
canonical: https://docs.rumoro.dev/integrations/ifttt
markdown: https://docs.rumoro.dev/integrations/ifttt.mdx
---

# IFTTT

Use Rumoro mentions in IFTTT Applets, and let Applets manage keywords and triage mentions.

With [IFTTT](https://ifttt.com), a new mention can reach the apps you already use: a phone notification, a row in Google Sheets, a message in Discord, a task in Todoist. Applets can also act on Rumoro, for example adding a keyword for every new product you list somewhere else.

| | |
| --- | --- |
| Triggers | New mention, New negative mention, New mention in a view |
| Query | History of mentions |
| Actions | Add keyword, Pause keyword, Resume keyword, Update mention status, Set mention relevance |
| Connection | Sign in to Rumoro and choose a workspace |

## Connect Rumoro

1. In IFTTT, open the Rumoro service and choose **Connect**.
2. Sign in to Rumoro. Choose the workspace IFTTT may use, read what it will be able to do, then choose **Allow**.

IFTTT then acts as you in that workspace, within what your role there allows. Members can use the triggers, the query and the two mention actions. Adding, pausing and resuming keywords needs an owner or admin. IFTTT can read your mentions, keywords and saved views, triage mentions and change keywords, nothing else: not alerts, the team, API keys or billing.

The connection is an API key named `IFTTT (your email)` on the [API keys](https://app.rumoro.dev) page. It doesn't expire. It stops working when:

- a workspace owner revokes it on the API keys page,
- you connect IFTTT to the same workspace again (the new connection replaces the old one), or
- you leave the workspace.

## Which mentions fire a trigger

The mention triggers and the query list the mentions an [instant alert](/alerts) would send, newest first by the time Rumoro matched them:

- **Relevant.** The classifier scored them 40 or more, counting your own corrections.
- **Open.** Mentions you marked done or ignored before IFTTT saw them don't fire.
- **Collected.** A new keyword's [look-back](/how-it-works) never fires a trigger, so adding a keyword doesn't flood your Applets with older posts. Look-back mentions stay in your feed.
- **Not muted.** Posts by people you muted are left out.

A mention fires only once it has been scored, so its relevance, sentiment and intents are always filled in.

A mention fires once it has been scored. Rumoro then tells IFTTT through its Realtime API, usually within a minute, so your Applets don't wait for IFTTT's own polling schedule. A post that matches two of your keywords is two mentions and fires twice, as with webhooks.

## Triggers

**New mention** fires for each new relevant mention. **New negative mention** fires only for those the classifier scored negative.

| Field | Values |
| --- | --- |
| Keyword | Any keyword, or one of your keywords |
| Platform | Any platform, or one of the 16 sources (12 platforms and 4 review sources) |
| Intent | Any intent, or one of the 15, such as buying intent, question, complaint, churn intent or bug report |

**New mention in a view** fires for each new mention in one of your [saved views](/guides/views), so any filter you can save works in IFTTT: follower counts, engagement, languages, review ratings, several intents at once. A view without its own relevance condition (`relevant` or `minRelevance`) gets the default of 40, and one without a `status` condition gets open mentions only. A view of noise (`relevant: false`) fires for scored noise.

Ingredients of the triggers and the query:

| Ingredient | Example |
| --- | --- |
| `MentionId` | `mm_7c1f…` (use it in the two mention actions) |
| `Text` | The post's text. A long post shows the passages around your keyword |
| `Title` | The post's own title where the platform has one, else empty |
| `PostUrl` | `https://news.ycombinator.com/item?id=…` |
| `ImageUrl` | The post's image, where it has one |
| `Platform` | `Hacker News` |
| `AuthorName`, `AuthorHandle`, `AuthorUrl` | The author, where the platform gives one |
| `AuthorFollowers` | The author's follower count, where the platform gives one |
| `Keyword` | The keyword that matched |
| `Sentiment` | `positive`, `neutral` or `negative` |
| `Relevance` | `0` to `100` |
| `Intents` | `Question, Pricing`, or empty |
| `WhyItMatters` | The classifier's note, up to 200 characters |
| `Language` | An ISO 639-1 code such as `en` |
| `Rating`, `ReviewTitle` | A review's stars and title; empty for other posts |
| `PublishedAt` | When the post was published, ISO 8601 |
| `MatchedAt` | When Rumoro matched it, ISO 8601 |
| `DashboardUrl` | The mention in Rumoro |

## Query

**History of mentions** lists the same mentions, newest first, with the fields Keyword, Platform, Intent and Sentiment (any, positive, neutral or negative). Use it in an Applet's filter code to look back before acting.

## Actions

| Action | Fields | What happens |
| --- | --- | --- |
| Add keyword | Term (2 to 80 characters); Kind (brand, competitor or topic), Platform and Context (up to 300 characters for the classifier) may be left blank | Starts tracking the term: as a brand on every platform when left blank. If the term is already tracked, the Applet succeeds and nothing changes |
| Pause keyword | Keyword | Stops collection for the keyword, as muting it in Rumoro does |
| Resume keyword | Keyword | Starts it again |
| Update mention status | Mention id (the `MentionId` ingredient), Status (open, done or ignored) | Sets the mention's status, as in your feed |
| Set mention relevance | Mention id, Relevance (relevant or not relevant) | Your verdict: not relevant sets relevance to 0 and drops it from the relevant feed, relevant sets it to 100 |

Keywords added or resumed from IFTTT are billed like any other: $5 per keyword per 30 days, plus $0.008 per matched mention ([billing](/billing)). When the balance cannot cover a day of your keywords, Add keyword and Resume keyword fail with "Add funds first: …", which IFTTT shows in the Applet's activity.

## Limits and errors

- IFTTT's requests count toward your workspace's [600 requests a minute](/rate-limits), shared with the REST API and MCP.
- IFTTT shows Rumoro's error messages in the Applet's activity, for example "Your workspace role does not allow this operation." or "Keyword not found".
- If an Applet stops with "Connect Rumoro again", its connection was revoked or replaced. Reconnect Rumoro in IFTTT.