Actions

An Action is a task you configure once and reuse. Sending a Slack message when a signup lands, enriching a company from its domain, scoring a lead against your ICP, mailing a weekly digest: all of these are actions.

You add one from the catalog, configure it, and it lives in Your Actions where you can run, edit, pause, or delete it.

Actions replace the older Triggers and Robots. Any trigger you had was converted into a Send Notification action with the same event and the same destination, so existing notifications keep working. Nothing delivers twice.

What an Action Is Made Of

Read it left to right: sources, then what happens, then where the result goes.

Sources are where the action reads from. Today that means your projects.

Schedule and triggers decide when it runs. A schedule runs it on a cadence you set with a cron expression. Triggers run it when something happens: an event arrives, or Logspot records a signal. Tasks that support it can also be run by hand at any time.

Task is what it does, and is the catalog entry you picked.

Agents are the reasoning, for tasks that need it. An action can have none, one, or several. A template digest has no agent. Build Company Profile has two that work together.

Context is what an AI task knows: your Company Profile, plus any additional instructions for that one action.

Destinations are where the result goes: Slack, Discord, email, Telegram, a webhook, Clay, or HubSpot. You set them on the Destinations tab. An AI task can also skip delivery and keep its result in the Activity Log.

Send Notification

This is the one most people want first. It uses 1 Action per notification, no Data Credits, and is included on the Essentials plan and up.

1. Go to Actions → Browse Catalog, choose Send Notification, and click Add & Configure.
2. On the Basics tab, choose Add Trigger and enter the event name to match, such as Signup Completed, or pick a signal.
3. On the Destinations tab, set Destination to Slack, Discord, Email, Telegram, Webhook, Clay, or HubSpot, and save.
4. In Your Actions, open the action's menu and choose Send Test to check the destination. A test webhook carries an x-logspot-test: true header, so your endpoint can tell it from a real delivery.

When a matching event arrives, Logspot applies the consent gate and delivers. Delivery fires once per event even though the underlying queue can deliver a message more than once, so you will not get duplicate alerts.

Each notification uses 1 Action, however many destinations it reaches. Retries and Send Test are free, a notification that could not be sent to any destination costs nothing, and notifications keep sending when your Actions allowance runs out.

Triggers and Cooldown

An action can have up to ten triggers, and any one of them starts it. Each trigger is one of these:

• Event fires when an event with that name arrives.
• Signal fires when Logspot records a signal of that type. Under Which Accounts, choose Target Accounts Only to react only to signals about your target accounts, or All Accounts. Signal triggers are being enabled account by account, alongside Signals.

Cooldown stops overlapping triggers from repeating the same work. The choices are Every Occurrence, 15 Minutes, 1 Hour, 24 Hours, and 7 Days. With 1 Hour, an action runs about once per company in each hour, however many of its triggers fire. Every Occurrence runs on each match, and a notification for an event Logspot cannot tie to a company always sends. Send Notification starts at Every Occurrence, and AI tasks start at 1 Hour.

AI Tasks on Triggers

Prospect Research, Lead Qualification, and Outreach Draft can run from triggers. When a trigger fires, the task runs for the company behind the event or signal and sends its result to the action's destinations. Each run spends credits, the same as running it by hand.

A triggered AI task only runs when Logspot knows the company and has its name or website, and each AI action runs at most 100 times a day from triggers. The cooldown applies too, so a busy account is researched once per window instead of once per matching event.

Chaining, which passed a signal on to an AI task, has been removed. Add a signal trigger to the AI action instead. Existing chains were converted this way automatically, with the cooldown set to Every Occurrence so each signal still runs the task once. An AI action that was set to run on an event or signal used to deliver only that event or signal, so it was converted to a Send Notification action that keeps doing exactly that, without spending credits.

The Catalog

The catalog holds thirteen task types. Eight appear in Browse Catalog; the rest run from the surface they belong to.

Five more exist but run from their own surfaces rather than the catalog: Build Company Profile and Account Watch run from Profiles and Target Accounts, Company Lookup and Person Lookup run from the enrichment surfaces, and Company Visitor Identification runs as visits arrive, in the projects you turn it on for under Actions → Enrichment.

You only see catalog entries your organization has access to, so your catalog may be shorter than this list.

Setting One Up

Pick a task from Browse Catalog and open its card with Add & Configure. The Set Up Action dialog has tabs, in order: Basics (name, triggers, cooldown), Sources (the project scope, your whole organization or specific projects), Destinations (where the result goes), Watched Accounts (Account Watch only), Agents, and Context. Add triggers or a schedule on Basics, choose the scope on Sources, and for AI tasks set the Company Profile and any additional instructions on Context.

Saving an action does not run it. Run Now is a separate, explicit button, and it appears only for manual tasks that can run straight from their saved configuration.

Your Actions has two tabs. Library lists your saved actions, with a scope column so you can tell organization-wide actions from project-specific ones. Actions of the same type are grouped into one row that expands to the individual actions, and a group surfaces any problems first, so a failure is not hidden when the group is collapsed. The Last Run column shows each action's most recent run, including why a run failed. Activity Log is the run history, and each run opens to its detail.

The Company Profile

AI tasks work from a Company Profile: structured intelligence about a company, including its ICP, value propositions, and competitors.

Our Profiles describes your own company. One is the default, and that is the context fed to AI agents automatically. Target Accounts describes the companies you sell to, in the same shape without your strategy overlay.

You build or refresh a profile from a website, so refreshing needs the profile to be linked to a real one. If it is not, rebuild it from Profiles instead.

What Costs Credits

Two meters move independently.

Actions is a value-based unit. Each task type has a fixed Actions cost.

Data Credits is a cost-based unit, covering the real model and data cost of a run. AI tasks reserve a conservative estimate first, then settle to what the run actually cost. If a task fails after being charged, both meters are refunded.

A notification uses 1 Action and no Data Credits. AI tasks and data lookups use both meters. When an AI task delivers its result, the delivery is part of that task's cost. Sending to HubSpot adds nothing. Your organization's first Company Profile build is free.

See Actions & Data Credits.

Consent

Every action declares the consent it requires before it runs. An action that sends data onward for advertising only runs for events carrying marketing consent. Logspot checks the event's recorded permissions and the person's current consent before executing, so an automation never acts on data the person did not allow. See Consent Management.

A Note on the Notify Flag

Older SDK examples set notify: true on a track call to fire a notification without matching an event name. Nothing reads that flag now. It is still accepted so SDKs sending it do not error, and it is still stored, but it fires nothing. Match on the event name instead when setting up a Send Notification action.

Related

• Receiving Webhooks
• Data Credits
• Consent Management