Expert Agentic Application Building Soft-Launch Access

FlowFuse Expert Agentic Application Building (agentic Node-RED development, FlowFuse 2.30) is in soft launch on FlowFuse Cloud. Access is granted on request to teams on a paid plan (Starter, Team, Enterprise). This page describes how to triage incoming requests.

Customers request access via the contact form linked from the 2.30 release blog post and the changelog. They are asked to include the email associated with their FlowFuse Cloud team.

Ownership

Flow

flowchart TD
    Start(["Reads soft-launch announcement<br />Includes FlowFuse team email"])
    Contact["Contact submitted<br />HubSpot notification fires"]
    Identify["<b>[Triage]</b> Identify customer and team"]

    AskSignup["<b>[Triage] Reply: not a customer yet</b><br />- Direct to sign-up on a paid plan<br />- Ask for use case for fit"]
    AskRelated["<b>[Triage] Reply: clarify related team</b><br />- Which team should be enabled?<br />- Ask for use case"]
    AskFreeOrExpired["<b>[Triage] Reply: free or inactive plan</b><br />- Upgrade or reactivate required<br />- Ask for use case"]
    AskPaid["<b>[Triage] Reply: request info</b><br />- Ask for use case"]

    Receive["<b>[Triage]</b> Receive reply<br />Use case and reason on file<br />Paid tier path confirmed"]
    InformProduct["<b>Inform Product</b><br />Add note on HubSpot record<br />summarising the use case"]

    Eligibility{"<b>[Triage]</b> Verify eligibility<br />Fit for soft-launch<br /><i>If any doubt: loop Product in via the HubSpot note</i>"}
    Decline(["<b>[Triage] Reply: not eligible</b><br />Polite decline, explain criteria"])
    PCR["<b>[Triage]</b> Open PCR for activation<br />CloudProject issue, pre-filled body"]
    Activate["<b>[Engineering]</b> Activate feature for team<br />Comment back on PCR"]
    Notify(["<b>[Triage]</b> Notify contact<br />Access is live"])

    Start --> Contact --> Identify
    Identify -- "Not a customer yet" --> AskSignup
    Identify -- "Different email,<br />related team exists" --> AskRelated
    Identify -- "Free plan or<br />plan no longer active" --> AskFreeOrExpired
    Identify -- "Found, paid plan active" --> AskPaid
    AskSignup --> Receive
    AskRelated --> Receive
    AskFreeOrExpired --> Receive
    AskPaid --> Receive
    Receive --> InformProduct --> Eligibility
    Eligibility -- "Not eligible" --> Decline
    Eligibility -- "Eligible" --> PCR
    PCR --> Activate
    Activate --> Notify

    classDef default fill:#e5e7eb,stroke:#6b7280,color:#1f2937
    classDef product fill:#e9d5ff,stroke:#7e22ce,color:#581c87
    classDef decision fill:#fef08a,stroke:#a16207,color:#713f12
    classDef decline fill:#fecaca,stroke:#b91c1c,color:#7f1d1d
    classDef engineering fill:#fed7aa,stroke:#c2410c,color:#7c2d12
    classDef success fill:#86efac,stroke:#15803d,color:#14532d

    class InformProduct product
    class Eligibility decision
    class Decline decline
    class PCR,Activate engineering
    class Notify success

Step by step

1. [Triage] Identify customer and team in HubSpot using the email from the contact submission. Four outcomes:

   • Not a customer yet: no FlowFuse Cloud team for this contact or their company.
   • Different email, related team exists: the contact's email doesn't match, but a team at the same company exists under a different email (e.g. a colleague's Starter team).
   • Free plan or plan no longer active: the team exists but is on the Free plan, or a previously paid plan / trial has expired or been cancelled.
   • Found, paid plan active: the team is on Starter, Team, or Enterprise with an active subscription.

2. [Triage] Reply with an info ask, scoped to what is still missing. The paid tier requirement always lands in this first reply so it never arrives late in the conversation. Use the relevant template below.

3. Inform Product as soon as the use case is on file. Add a note to the HubSpot contact record summarising the request (team name, use case in one or two sentences, plan tier) and mention Product on the note so they are notified. Keep the conversation in HubSpot; do not move it to Slack.

4. [Triage] Verify eligibility once use case, reason, and paid tier path are all on file. Eligibility checks fit for the soft-launch (intended use, team readiness, paid plan in place or being arranged). Eligibility runs only after all info is in.

   • If you have any doubt about fit, loop Product into the decision by adding them to the same HubSpot note thread. Product owns the criteria; triage should not make borderline decisions alone.

5. Outcome:

   • Eligible: [Triage] open a Production Change Request in CloudProject. Tick Production in the Environment checkbox.
   • Not eligible: [Triage] reply with a polite decline using the template below.

6. [Engineering] Activate the feature for the team referenced in the PCR and comment back on the PCR when complete.

7. [Triage] Notify the contact that access is live.

Reply templates

Adapt to tone and context. The shape of the ask is what matters.

A. Not a customer yet

Subject: FlowFuse Expert Agentic Application Building

Hi [name],

Thanks for your interest. It looks like [company name] doesn't have a FlowFuse Cloud team yet. Expert Agentic Application Building runs on top of FlowFuse Cloud, so we'd need a team in place on a paid plan (Starter, Team, Enterprise) before we can enable the feature. Happy to walk through plan options and help get set up.

In the meantime, your use case helps us confirm fit: what you want to build, why you need it, what you plan to do with it, plus any other context you'd like to share.

B. Different email, related team exists

Subject: FlowFuse Expert Agentic Application Building

Hi [name],

Thanks for your interest. The email you used doesn't match a FlowFuse Cloud team directly, but I can see [company name] has a [Starter / Team / Enterprise] team active under a different email. A couple of things to sort out:

• Should we enable Expert Agentic Application Building on that existing team, or are you looking to set up a separate one? Happy to walk through either path.
• Your use case: what you want to build, why you need it, what you plan to do with it, plus any other context you'd like to share.

C. Free plan or plan no longer active

Subject: FlowFuse Expert Agentic Application Building

Hi [name],

Thanks for your interest. We found your [team name] team on FlowFuse Cloud. Two things before we move forward:

• Expert Agentic Application Building is currently available on FlowFuse Cloud paid plans (Starter, Team, Enterprise). Your team is on the Free plan today / your previous plan is no longer active, so it'll need to be upgraded or reactivated before we can enable the feature. Happy to walk through plan options.
• Your use case: what you want to build, why you need it, what you plan to do with it, plus any other context you'd like to share.

D. Found, team is already on a paid plan

Subject: FlowFuse Expert Agentic Application Building

Hi [name],

Thanks for your interest. We found your [team name] team on FlowFuse Cloud. To confirm fit for the soft launch, could you share your use case: what you want to build, what you plan to do with it, plus any other context you'd like to share?

Once we have that we'll enable Expert Agentic Application Building on your team.

E. Decline (not eligible)

Subject: FlowFuse Expert Agentic Application Building

Hi [name],

Thanks for sharing your use case. Right now [specific reason], so we're not enabling it on your team at this stage.

We'll be expanding access over the coming weeks. If your situation changes, reach back out and we'll re-evaluate.

Edge cases

• Contact never replies to the info ask: [Triage] treat as stalled. Follow up on the standard cadence; close the loop after the cadence is exhausted.
• Found-tier classification is ambiguous (e.g. trial about to expire, plan change in flight): [Triage] treat as Free tier and include the paid tier note.
• Eligibility genuinely borderline or use case is unusual: [Triage] loop Product into the HubSpot note before deciding. Better to slow one case down by a day than ship a no/yes Product would have flipped.
• Decline appeals: [Triage] handle out of band. The decline reply explains the criteria so the customer can return with new context if their situation changes.
• Engineering activation fails or is delayed: Engineering comments back on the PCR; triage keeps the customer informed.