FlowRunner
PricingContact
Theme
Start Free

Valuecase

Sales Outreach

Connect AI agents to Valuecase, a digital sales room platform for B2B deals. Agents create buyer-facing spaces, set custom properties per deal, and read or write the forms a buyer completed inside the room.

16 actions Custom auth available
A deal reaches the stage where a buyer-facing room is warranted in the CRM
Agent reads the company name, primary contact and deal attributes from the CRM record
Create Space builds the room from the chosen template and returns its slug, URL and auth token
Add Space Integration ID Mapping links the space back to the CRM deal ID for later lookup
List Space Custom Properties confirms the per-deal personalization landed as intended
Deal owner receives the personalized room, the resolved properties and the share link
Deal owner confirms what the buyer will see before the link is sent outside the company

What This Integration Enables

Everything this connector creates is a page a customer will open. That is the fact worth designing around, and it separates Valuecase from the internal-facing tools sitting next to it in a sales stack. A space is not a record; it is a shared workspace with your company's name on it, populated with personalization that a buyer will read as a statement of how carefully you are handling their deal.

Agents create spaces from a template with the buyer company and primary contact supplied, either synchronously with Create Space, which returns the finished space, or through Create Space Async, which enqueues the work and returns a request ID that Get Async Space Status polls and Get Active Async Requests enumerates. They list spaces with filters on name, owner, team access, template, external integration ID and dates, optionally including engagement scores, custom properties and forms in the result. They update a space by slug, including archiving it and toggling share and download restrictions, and they delete one permanently. They attach and remove external system ID mappings so a space can be found later by its CRM deal or opportunity ID, and they read and update the per-space custom properties that carry deal-level personalization. On the buyer side they list forms across spaces filtered by completion date, read submissions, create or update a submission, and revert one to its previous state.

Two implementation facts change how a flow is built. Spaces are addressed two ways: Update Space, Delete Space and the custom property actions take the space slug, while the integration ID mapping actions take the space id, and List Spaces returns both. And the Create Space response includes a url alongside an authToken, where the shareable link is the URL with that token appended as the token query parameter. The token is the access control. There is no trigger and no published webhook subscription contract here, so a flow that needs to notice buyer activity polls List Spaces filtered by update date, or List Forms filtered by completion date, on a schedule.

Without FlowRunner

Rooms built manually per deal A sales room is created when a rep has the time, so the fastest-moving deals get the thinnest ones
Rooms detached from the CRM Finding the room for a deal means searching by company name and hoping it is the right one
Buyer form answers stranded What a buyer filled in inside the room stays inside the room until somebody opens it

With FlowRunner

A room per deal, built on stage change Create Space runs from the CRM record, so the personalization comes from the deal rather than from memory
Rooms addressable by deal ID Add Space Integration ID Mapping makes the CRM ID the lookup key for the space
Form answers routed onward Get Form Submissions pulls what the buyer completed into the systems that act on it

Use Case Scenarios

A room created from the deal, not from a template dropdown

A deal in HubSpot or Pipedrive moves to the stage where a buyer needs a shared workspace. The agent reads the company, the primary contact and the deal attributes, calls Create Space against the right template, then immediately calls Add Space Integration ID Mapping with the CRM deal ID so the space is findable by that ID forever after. It writes the per-deal personalization with Update Space Custom Property and reads it back with List Space Custom Properties to confirm the values took the shape the tenant definition expects, single-value or multi-value. The room exists within the same flow run that moved the deal.

Buyer form answers that reach the people who act on them

A buyer completes a security questionnaire or a technical requirements form inside their space. On a schedule the agent runs List Forms filtered by completion date, pulls the answers with Get Form Submissions, and routes them onward: a summary to the deal channel in Slack, the requirements onto the deal record, and a task for the solutions engineer. Because the Valuecase Public API document does not publish the submission body shape, the raw response is passed through as received, so the flow reads it defensively rather than assuming a schema it was never given.

Creating rooms in bulk without blocking

A campaign produces two hundred qualified signups that each warrant a room. The agent uses Create Space Async so each request returns a request ID rather than waiting for generation, tracks the outstanding work with Get Active Async Requests, and polls Get Async Space Status until each reaches a terminal state. Completed spaces get their CRM mapping attached and their custom properties set. Failures are collected and reported as a list rather than silently missing from the batch.

Human-in-Loop Highlight

The gate on Valuecase is the moment the share link leaves the company, and it exists because of what the API does not offer. Create Space returns a url and an authToken, and the shareable link is that URL with the token appended as the token query parameter. That token is the access control on a room containing a named buyer's company, their contact, deal-specific personalization and eventually their submitted forms. Nothing in this surface rotates or reissues it. Update Space can toggle share and download restrictions, and Delete Space removes the room permanently and cannot be undone, but there is no way to invalidate one link and mint another for the same space. So a wrong link, or a right link sent to a wrong recipient, is not something the connector can quietly correct. The agent therefore builds the room and stops before the send. It posts to the deal owner: "Space for [buyer company] is ready. Primary contact [name], template [name], custom properties resolved to [values], mapped to CRM deal [id]. The share link carries its own auth token and cannot be reissued. Send it to [address], change the recipient, or hold." The owner confirms, and the agent hands the link to the email step. Creating, mapping and personalizing run unattended. Handing a buyer their key does not.

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

Agent Capabilities

16 actions

Spaces

7
  • Create Space Creates a new Valuecase space (digital sales room) from a template. Pass the Template ID plus the buyer company name and primary contact name to personalize the space. The response includes the space slug, the shareable URL, and an auth token that must be appended as the token query parameter when sending the space link to an external recipient.
  • Create Space Async Enqueues creation of a new space from a template and returns immediately with a request ID. Use Get Async Space Status to poll for completion. Prefer this over Create Space when creating many spaces so the request is not blocked while the space is generated.
  • Get Async Space Status Returns the status of an asynchronous space creation request created with Create Space Async. Poll this until the request reaches a terminal state.
  • Get Active Async Requests Returns all non-terminal asynchronous space creation requests for the current user. Use this to see space creations that are still queued or in progress.
  • List Spaces Lists spaces with optional filtering and pagination. Filter by name, owners, team access, template, external integration ID, or creation and update dates, and optionally include engagement scores, custom properties, and forms in each result. This is the operation a scheduled flow polls, since the service ships no trigger.
  • Update Space Updates a space identified by its slug. Owner ID is required by the API. Optionally archive the space or toggle the share and download restrictions.
  • Delete Space Permanently deletes a space identified by its slug. This action cannot be undone, and it takes the room's form submissions with it.

Integration ID Mappings

3
  • Add Space Integration ID Mapping Attaches an external system entity ID to a space so it can be looked up later by that ID, for example a CRM deal or opportunity ID. The third party type for added mappings is Custom.
  • Get Space Integration ID Mappings Returns the external system entity ID mappings attached to a space.
  • Delete Space Integration ID Mapping Removes an external system entity ID mapping from a space. All four fields must match the mapping being removed.

Custom Properties

2
  • List Space Custom Properties Lists the custom properties set on a space. Each property is either single-value or multi-value depending on the tenant-level custom property definition.
  • Update Space Custom Property Updates a single custom property on a space by its key. Provide either a single value or a list of values depending on whether the property is single-value or multi-value in the tenant definition. If a list of values is provided it takes precedence.

Forms

4
  • List Forms Lists forms across spaces with optional filtering and pagination. Filter by the spaces they belong to, by completion date, and optionally include the form submissions and not-yet-completed or deleted forms.
  • Get Form Submissions Returns the submissions for a form, identified by its form node ID. The submission payload shape is not published in the Valuecase Public API document, so the raw response is returned as received.
  • Create or Update Form Submission Creates a new form submission or updates the existing one for a form node. The submission body shape is not published in the Valuecase Public API document, so the submission data is passed through as provided and the raw response is returned.
  • Revert Form Submission Reverts a form submission to its previous state, identified by the form node ID and the submission ID.

Frequently Asked Questions

What can FlowRunner do with Valuecase?

FlowRunner agents can run Create Space, Create Space Async, and Get Async Space Status in Valuecase, plus 13 more actions.

Does connecting Valuecase to FlowRunner require OAuth?

Valuecase uses a custom authentication method to connect to FlowRunner.

Can Valuecase trigger a FlowRunner workflow automatically?

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

Start building with Valuecase

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