# App events: let a tool you use fill a list or the Inbox Source: https://listplus.ai/en/help/lists-and-import/app-events Last updated: 2026-10-11 An **app event** is something that happens in a tool you already use — a message in a Slack channel, a new Typeform answer, a Calendly booking — and arrives in ListPlus by itself. You pick the app and the event; there is no address to copy and nothing to build. One app event has one destination, and the destination is the place you set it up in: - **In a list** → what arrives becomes a record of that list. - **In the Inbox** → what arrives becomes an Inbox entry for you to look at. If you would rather send records from your own automation (Zapier, Make, n8n, your own code), use a list webhook instead — see "List webhooks: receive records from forms and tools". ## Setting one up - **For a list:** open the list, click **Set up** next to its name and choose **App events**. (A list that already has one also shows it on its page in the Inbox.) - **For the Inbox:** in the Inbox, with no entry selected, open the setup page; **App events** is the first card. Click **Add app event**. The dialog asks one thing after the other, and each choice folds into a line you can change: 1. **App** — Slack, Typeform, Calendly, Tally, Jotform, Webflow or Gmail; **Another app …** searches the other apps. 2. **Account** — the connected account to use, or connect one. With only one account for the app this step is skipped. 3. **Event** — what should arrive, for example "New Message In Channels". **Show all events** lists the app's other events. The event names come from the app's connector and are in English. 4. **Settings** — what the event needs, for example the Slack channel or the form. 5. **Preview** — the latest event as it will arrive: as an Inbox entry, or with its fields and the columns they go to. If the tool has nothing to show yet, the preview says so. Nothing arrives and nothing is charged until you click **Activate**. Closing the dialog before that discards the setup. Events from before the moment you activate are not brought in. ## What arrives in a list **A finished record** — a form answer, a booking, a new contact: its fields are placed in the list's columns the way a list webhook places them. Known names (email, first name, company …) go to their column, names ListPlus has not seen before are placed by AI once and remembered, and fields without a column are kept with the record. A record that matches an existing one fills that record's empty fields instead of adding a duplicate. **A message** — a Slack message, an e-mail: it has no fields, so it is read for contacts first. Every message becomes an Inbox entry; if it names a contact, ListPlus recognizes it, and whoever comes with **enough to work with** — an e-mail address, a LinkedIn profile, or a name with a company — is added to the list by itself. The entry then shows where the contact went. Anything else — a message that names nobody, a name without a company — stays in the Inbox as an entry for you, where you can recognize or complete it by hand. In the list, your triggers run for these records like for any other new record — so a lead someone reports in Slack can be enriched and passed on by a pipeline without anyone touching it. ## What arrives in the Inbox A message becomes an entry with its text, the channel and the sender; any other event is kept whole. From there it is an Inbox entry like any other: you click **Recognize contacts** and decide what happens with them. The Inbox itself never adds contacts to a list by itself. ## Reporting leads in Slack — an example 1. Create a Slack channel, for example #leads, and a list "Reported leads". 2. In the list: **Set up** → **App events** → **Add app event** → **Slack** → **New Message In Channels** → choose the channel → **Activate**. 3. A colleague writes "Ralf Hertneck, CloudValues" in the channel. 4. The contact appears in the list. A trigger "a record is new in the list" can hand it to an Enrich pipeline, and a second trigger can send the enriched contact on, for example to your CRM. **Condition.** If the channel carries more than leads — or tools post into it — enter a text under **Condition**, for example a code word: only messages that contain it arrive, and the others are neither delivered nor charged. Upper and lower case count. Without a condition every message of the channel arrives. Replies in threads are never read for a list. Bot messages can be left out in the event's settings (**More settings**); leave them in if a tool posts your leads. ## The list of your app events Each app event is a line with the app, the event, its setting, when something last arrived, how many events arrived in the last 24 hours and its state. The **⋯** menu has **Pause**, **Resume** and **Remove**. Pausing stops the tool from delivering, so nothing is charged while paused; removing also takes the event down in the tool's connector. What already arrived stays. An app event can stop by itself and say so: **Stopped: no credits** or **Stopped: plan no longer covers it**. Top up or change the plan, then click **Resume**. ## Plan, price and limits - **Plan:** app events use a connected tool, so they need **Pro** or Premium, like every connected tool. - **Price:** every event received costs credits — also a record that is merged into an existing one or held back, because the delivery happened. For a message that is meant for a list, recognizing its contacts costs credits on top, only when the message names a contact. Setting up, the preview and a paused app event cost nothing. The amounts are in the price list ("What does an app event cost?"). - **Limits:** up to 120 events per minute per app event; an event of up to 256 KB. Records that go into a list have a daily limit per workspace: 5,000 on Pro and 50,000 on Premium (the same amounts as for list webhooks, counted separately). An event the list or the Inbox cannot take because a limit is reached is not charged. **Related topics:** list-webhooks · inbox · send-to-inbox-from-tools · recognition-and-review · price-list · connect-crm-and-sheets. ## FAQ ### What is an app event? Something that happens in a tool you use — a Slack message, a new form answer, a booking — and arrives in ListPlus by itself. You choose the app and the event; there is no address to copy and no automation to build. Set up in a list it becomes a record of that list, set up in the Inbox it becomes an Inbox entry. ### How do I set up an app event? For a list, open it, click Set up and choose App events; for the Inbox, open its setup page, where App events is the first card. Click Add app event, choose the app, the account, the event and its settings, check the preview and click Activate. Nothing arrives or is charged before you activate. ### Which apps can I connect as an app event? Slack, Typeform, Calendly, Tally, Jotform, Webflow and Gmail are offered first, with events ListPlus has checked. Another app … searches the other apps; their events arrive as records whose fields are placed automatically, without ListPlus having checked each one. Google Sheets' "new row" event is not offered first because it sends no column names. ### Can a Slack message add a contact to a list automatically? Yes — add the app event in the list (Set up → App events → Slack → New Message In Channels) and choose the channel. Each message is read for contacts; whoever comes with an e-mail address, a LinkedIn profile, or a name with a company is added to the list by itself. A message that names nobody, or a name without a company, stays in the Inbox as an entry for you. ### Can I limit a Slack channel to certain messages? Yes — enter a text under Condition when you set the app event up, for example a code word. Only messages that contain exactly this text arrive (upper and lower case count); the others are neither delivered nor charged. Leave the condition empty and every message of the channel arrives. ### What counts as "enough" for a contact to be added automatically? An e-mail address, a LinkedIn profile, or a name together with a company. With that the list — and an enrichment after it — can find the person again. A first name alone, a name without a company, or only a company is not enough: the message stays in the Inbox as an entry, where you can recognize or complete it by hand. ### Does an app event cost credits? Yes: every event received costs credits when it arrives, also when the record is merged into an existing one or held back. For a message that is meant for a list, recognizing its contacts costs credits on top, only when the message names a contact. Setting up, the preview and a paused app event cost nothing; the amounts are in the price list. ### Which plan do I need for app events? Pro or Premium. App events use a connected tool, and connected tools are not part of Basic. If the plan no longer covers an app event it stops and shows "Stopped: plan no longer covers it"; after changing the plan, click Resume. ### Do I have to map the fields of an app event to my columns? No. Fields are placed the way a list webhook places them: known names go to their column, names ListPlus has not seen are placed by AI once and remembered for that app event, and fields without a column are kept with the record. The preview shows where the latest event's fields go before you activate. ### Does an app event create duplicates? No. A record that matches an existing one — by e-mail, LinkedIn, phone, or name and company — fills that record's empty fields instead of being added again. This also applies to contacts recognized in a message. ### Are older messages or form answers brought in when I activate? No, only what happens after you click Activate arrives. The preview may show the latest existing event so you can see what will come, but it is not added. To bring in what is already there, import it once. ### Why did an app event stop? Because the workspace ran out of credits or the plan no longer includes connected tools; ListPlus then asks the tool to stop delivering, so nothing more is charged, and the line shows the reason. Top up or change the plan, then choose Resume in the app event's ⋯ menu. Events that happened while it was stopped are not brought in afterwards. ### How do I pause or remove an app event? Open the ⋯ menu on its line and choose Pause, Resume or Remove. Pausing stops the tool from delivering: nothing is charged while paused, and what happens meanwhile is not brought in later. Removing deletes the app event for good; records and Inbox entries that already arrived stay. ### What is the difference between an app event and a list webhook? An app event needs no setup in the other tool: you pick the app and the event in ListPlus. It costs credits per event and needs Pro. A list webhook is an address you paste into a form tool, Zapier, Make, n8n or your own code; it is free on every plan, and you build the sending yourself. ### Do triggers and pipelines run for records from an app event? Yes. A record that arrives through an app event is a new record of the list like any other, so triggers such as "a record is new in the list" run and can hand it to a pipeline — for example to enrich it and pass it on to your CRM or a Slack channel.