FlowRunner
PricingContact
Theme
Start Free

La Growth Machine

Sales Outreach

Run multichannel sales prospecting with La Growth Machine, covering campaigns and stats, audiences, leads and enrichment, and the LinkedIn and email inbox. Agents build the audience and work the replies in one system.

34 actions API key available
La Growth Machine website ↗ Capability data verified 2026-08-02
A lead arrives from a LinkedIn import or an inbound signal and is proposed for an audience
Agent resolves the person with Search Lead, which matches in priority order across lead id, CRM id, LinkedIn identifier, email and finally name plus company
Agent calls Search CRM to pull the matched record with its deals, lifecycle stage and recent activities
Agent reads prior outreach with Get Lead Logs so a new sequence does not repeat what an earlier one already said
Agent reads the enrichment balance with Get Credits before spending on a lookup that may not be needed
Agent reports the conflict, naming the open deal, its stage and the rep who owns it
That rep decides whether the lead is enrolled, held, or taken out of the audience entirely

What This Integration Enables

La Growth Machine is built around two things most outreach platforms treat as afterthoughts: the sending identity and the inbox. Identities are the named LinkedIn and email personas that campaigns and manual sends go out as, and member ids attribute individual actions and enforce permissions, so activity stays traceable to a person rather than to a platform. The inbox behaves like something a sales team actually works, with search across identity, lead, audience and campaign, per-conversation notes the team reads alongside the thread, plus archive, snooze and unsnooze. It is a rep's tool that happens to run campaigns, not a campaign engine that happens to have an inbox.

The action that makes the difference in practice is Search CRM. La Growth Machine looks a contact up in the connected CRM, whether HubSpot, Pipedrive, Salesforce or another, and returns the matched record with its deals, lifecycle stage and activities. That is the one piece of context that decides whether a prospect should be contacted at all, and it is available before enrolment rather than after the damage. FlowRunner agents use it that way: build the audience, enrich only what needs enriching, and stop when the CRM says this account is already somebody's. Around it sits the full surface through FlowRunner connectors, covering campaigns and per-channel stats, audiences including LinkedIn search import, lead creation and status changes, credit-aware enrichment, and message sending on both channels.

Without FlowRunner

Prospecting collides with pipeline Outbound reaches a contact whose company already has a live deal with another rep
The inbox is a firehose LinkedIn and email replies for every identity arrive in one undifferentiated stream
Enrichment spend is unbounded Credits are consumed on leads that were never going to be contacted

With FlowRunner

Pipeline checked before enrolment A live CRM lookup runs before the lead enters an audience, not after the first message
The inbox is a work queue Conversations are filtered, noted, snoozed and archived by identity and campaign so each rep sees their own
Enrichment spend is deliberate The credit balance is read first and the cheaper enrichment type is chosen when it will do

Use Case Scenarios

Audience built from a LinkedIn search, checked against pipeline

An agent calls Import Audience From LinkedIn against a Sales Navigator search URL, using a named identity to perform the search. It watches the import status on Get Audience Detail until the job clears, then reads the collected people with Get Audience Leads, which returns professional and personal emails alongside the enrichment fields showing which provider found each address and how deliverable it is. Every lead then goes through Search CRM. Anyone attached to an open deal, a current customer record or a recent support activity is pulled out with Remove Lead From Audiences and reported to the owning rep. What remains is a genuinely cold audience, which is the only kind worth a cold sequence.

Enrichment that respects the budget

Enrichment is not free here, and the connector is explicit about it: a full lookup and an email-only lookup each spend more than a LinkedIn profile refresh. So the agent reads Get Credits first, including the perishable portion that expires soon, and chooses the cheapest enrichment that answers the question. Where only a professional email is missing it uses the email-only mode, which works from a name and company without an existing lead id. Where the profile is stale it uses the profile refresh instead. Polling mode returns a request id, and Get Enrich Result carries the enriched address and phone once the job completes. Spend follows need rather than list size.

A reply that becomes a decision, not a notification

An inbox webhook delivers a new reply. The agent reads the full exchange with Get Conversation Messages, writes a short summary onto the thread with Edit Conversation Note in append mode so the rep sees context without opening another tab, and classifies the outcome. Positives are routed to the owning identity's rep. Deferrals are handled with Snooze Conversation set to the date the prospect named, so the thread disappears now and returns when it is relevant. Closed conversations are archived. The inbox stays a work queue rather than a backlog, and every state change is recorded where the next person will find it.

Human-in-Loop Highlight

The expensive mistake in multichannel prospecting is not a bounce. It is a cold sequence landing on a contact whose company is already mid-negotiation with one of your own reps, and the prospect noticing that the left hand does not know what the right hand is doing. La Growth Machine gives an agent the ability to see that coming through Search CRM, which returns the matched record with its deals, lifecycle stage and activities before anything is sent. What it cannot do is decide what the conflict means, because "there is an open deal at this account" can mean back off entirely, or it can mean this is a different business unit and the rep would welcome the coverage. So the agent stops with the specifics: "Idris Kaya at Vantage Logistics matched a CRM record with an open opportunity at stage Proposal, owner Priya, last activity 4 days ago. He is queued for the EMEA Ops audience. Enrol, hold until the deal closes, or remove from audiences?" Priya answers, because it is her deal. If the answer is hold, the agent calls Update Lead Status to pause the lead across the campaigns it is enrolled in, and the paused state is recorded rather than remembered.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

34 actions

Account

3
  • List Members Returns the team members on the account with their id, name and display label. Member ids are required when sending LinkedIn messages, where they attribute the action and enforce permissions, and this is also the endpoint the vendor recommends for testing a key.
  • List Identities Returns the connected sending identities: the LinkedIn and email personas campaigns and inbox actions send from. Identity ids are required by the message-sending and audience-import actions, so most flows resolve them once at the top.
  • Get Credits Returns the credit balance split into the total available and the perishable portion that expires soon and is already counted in the total. Read this before a large enrichment run, since enrichment cost varies by type.

Campaigns

5
  • Get Campaigns Returns the multichannel campaigns with name, description, language, status, the audience each draws from and the identity it sends as. Paginate with skip and limit.
  • Get Campaign Retrieves one campaign with its name, description, language, status, launch timestamp, audience and sending identity.
  • Get Campaign Stats Returns engagement statistics: audience size, how many leads started, completed and converted, and a reply breakdown split by channel with contacted, replied and percentage figures for LinkedIn and email separately. The per-channel split is what tells you which half of a multichannel sequence is actually working.
  • Get Campaign Lead Stats Returns per-lead statistics showing each lead's profile fields and their status in the sequence. Paging is cursor-based on lead id, so pass the last returned id to advance rather than an offset.
  • Get Campaign Messages Returns the message templates that make up a campaign's sequence, each with its type, channel, body and subject, position and active flag. Used to audit copy or mirror a sequence elsewhere.

Audiences

5
  • List Audiences Returns every audience with its identifier, name and lead count. Audiences are the lead pools campaigns draw from.
  • Create Audience Creates an empty audience with a given name, ready for leads to be added individually.
  • Import Audience From LinkedIn Populates an audience from a regular search URL, a Sales Navigator search URL or a post URL. The named identity performs the search, so its LinkedIn session must be connected and the widget open, otherwise the call is rejected with an identity verification error. That constraint is worth handling explicitly in a flow rather than treating as a transient failure.
  • Get Audience Detail Retrieves one audience with its name, description, lead count, type, timestamps and the current import status, which is the field to watch after starting a LinkedIn import.
  • Get Audience Leads Returns a page of the leads in an audience with the full record: name, company, job title, location, industry, LinkedIn URL, professional and personal emails, phone, and enrichment fields showing which provider found the email and how deliverable it is.

Leads

6
  • Search Lead Finds leads by any combination of identifiers, matching in priority order from lead id through CRM id, LinkedIn identifier, email, and finally name plus company. When too many records match, the response says so and the search must be narrowed, which a flow should handle rather than taking the first result.
  • Create Or Update Lead Creates a lead or updates a matching one, optionally dropping it into a named audience. At least one identifier is required, and ten custom attributes are available for personalization data.
  • Update Lead Status Changes a lead's status inside the campaigns it is enrolled in, for example pausing it after a deal is won elsewhere. The response lists the outcome per campaign, so a flow can confirm the pause actually applied everywhere it needed to.
  • Remove Lead From Audiences Removes a lead from one named audience, several, or all of them. If the lead is not in an audience the call succeeds silently rather than erroring, which makes it safe to call defensively.
  • Get Lead Logs Returns a paginated activity log for one lead: every message sent and received with its type, status, channel, timestamp and the campaign, step and template it came from. This is how a flow avoids repeating what an earlier sequence already said.
  • Get Lead Conversations Returns every conversation attached to a lead, one per identity and channel, with status, last message timestamp and preview, and whether the lead has replied.

Enrichment

2
  • Enrich Lead Starts an enrichment request. The email-only mode finds a professional email and its deliverability and works from a name plus company without an existing lead id, the profile mode refreshes LinkedIn fields more cheaply, and the full mode does both. Polling mode returns a request id, synchronous mode waits and may time out, and webhook mode posts the result to your URL.
  • Get Enrich Result Retrieves the outcome of a polling-mode request. The status moves through pending to completed or failed, and once completed the enriched professional email, personal email and phone are available.

Messaging

2
  • Send LinkedIn Message Sends a text or voice message to a lead from a connected identity. Identify the recipient by lead id or LinkedIn URL, not both, and supply either message text or a hosted audio URL. The member id attributes the action and is used for permission checks.
  • Send Email Sends an email to a lead from a connected email identity. Both an HTML and a plain-text body are required, and supplying a reply target threads the message into the existing conversation rather than starting a new one.

Inbox

7
  • Edit Conversation Note Writes the note attached to an inbox conversation, the short annotation the sales team sees alongside the thread. Replace overwrites it, append adds a timestamped entry and trims the oldest content when the limit is reached. This is where an agent leaves context for a person.
  • Search Conversations Searches the unified inbox with free text plus identity, lead, audience and campaign filters, conversation status, the direction and channel of the last message, date ranges, and flags for replied, unsubscribed, favourite and read. Paging is cursor-based.
  • Get Conversation Messages Returns every message in a conversation in chronological order with channel, status, content, sender, direction and attachments. Used to read a full exchange before drafting a reply or classifying the outcome.
  • Archive Conversation Archives a conversation so it leaves the active inbox view, targetable by conversation id or by the lead's email address.
  • Unarchive Conversation Returns an archived conversation to the active inbox.
  • Snooze Conversation Hides a conversation until a given moment, when it reappears. Omitting the wake time snoozes it indefinitely. This is how a flow schedules a follow-up on the prospect's own stated timing without leaving the thread cluttering the inbox.
  • Unsnooze Conversation Wakes a snoozed conversation immediately and returns it to the active inbox before its scheduled time.

CRM

1
  • Search CRM Looks a contact up in the CRM connected to the account and returns the matched record with its deals, lifecycle stage and activities. Supply an email address, or a first name narrowed by last name, company or LinkedIn URL. This is the check that keeps prospecting from colliding with pipeline.

Webhooks

3
  • Create Inbox Webhook Registers a webhook that receives realtime inbox events for LinkedIn and email messages. The URL must be publicly reachable and answer POST with HTTP 200. Leave the campaign filter empty to receive events from every campaign. La Growth Machine does not publish the delivered payload schema, so read the raw request body.
  • List Inbox Webhooks Returns every configured inbox webhook with its identifier, name, target URL, event type, campaign filter and creation time.
  • Delete Inbox Webhook Removes an inbox webhook by identifier, after which no further events are delivered to its URL.

Frequently Asked Questions

What can FlowRunner do with La Growth Machine?

FlowRunner agents can run List Members, List Identities, and Get Credits in La Growth Machine, plus 31 more actions.

Does connecting La Growth Machine to FlowRunner require OAuth?

No. La Growth Machine connects to FlowRunner with an API key, no OAuth flow required.

Can La Growth Machine trigger a FlowRunner workflow automatically?

La Growth Machine doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with La Growth Machine

$100 in credits. No card required. Connect in minutes.