A2A INTEGRATION · CUSTOM TOOL

Use GitDealFlow A2A with Voiceflow

Conversational AI design + agent platform. Builders shipping voice + chat agents for customer-facing surfaces who want VC signal lookups inside the flow.

Crunchbase API: $20K/yr. GitDealFlow A2A: free, no signup.

Voiceflow's Knowledge Base + API Step lets you wire any HTTP endpoint into a conversation flow. Add GitDealFlow as a Function or API Block so a Voiceflow-powered support agent, sales assistant, or onboarding bot can surface live engineering signals when a user asks about a competitor or trending startup. Best fit for teams already shipping branded conversational AI on web/IVR/Slack who want to enrich their bot's knowledge with live alt-data without retraining.

Endpoint facts for Voiceflow users

Whatever wiring you choose, the target is the same single endpoint. These are the fixed facts; nothing on this page changes them:

Protocol	A2A JSON-RPC 2.0 (protocolVersion 0.3.0)
Endpoint URL	`https://signals.gitdealflow.com/api/a2a`
Skills exposed	5, mirrored 1:1 with the MCP server tools (trending, sector, lookup, summary, methodology)
Auth	None; free in perpetuity, read-only
Freshness	Recomputed weekly; responses carry the data-as-of date
Best Voiceflow path	Voiceflow has no native MCP client yet, so the custom-tool path below (a thin JSON-RPC call) is the way in.

API Block (in-flow HTTP call)

// Voiceflow Designer → API Block configuration
// Method: POST
// URL: https://signals.gitdealflow.com/api/a2a
// Headers: Content-Type | application/json
// Body (raw JSON):
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "message/send",
  "params": {
    "message": {
      "role": "user",
      "parts": [
        {"kind": "data", "data": {"skill": "{skill}", "args": "{args}"}}
      ]
    }
  }
}

// Variables:
//   {skill}, pulled from intent slot (one of: trending, sector, startup, methodology, receipts)
//   {args} , pulled from entity slot (sector slug or startup name)
//
// Capture response into {gitdealflow_response}, then route to:
//   - Speak/Send Text Block: "{gitdealflow_response.artifacts[0].parts[0].data.startups[0].name} is up {...}"
//   - Carousel Block: visual cards for each startup result

Voiceflow Functions (server-side handler)

// In Voiceflow Project Settings → Functions → New Function
// Function definition (JavaScript):
async function gitdealflow_query(args) {
  const body = {
    jsonrpc: "2.0", id: 1,
    method: "message/send",
    params: {
      message: {
        role: "user",
        parts: [{kind: "data", data: {skill: args.skill, args: args.args || {}}}]
      }
    }
  };
  const res = await fetch("https://signals.gitdealflow.com/api/a2a", {
    method: "POST",
    headers: {"Content-Type": "application/json"},
    body: JSON.stringify(body)
  });
  return await res.json();
}

// Then in your flow → Function Block → call gitdealflow_query with input mapping

What you can ask

Voice agent on a sales line: 'Tell me what's trending in fintech right now.'
Slack support bot: '/signal Roboflow' → returns live commit-velocity context.
Embedded web widget on a VC firm's site: 'Which dev-tools companies are accelerating this quarter?'
Onboarding bot for a portfolio analytics product: prefills a watchlist with our top 5 trending each session.
IVR fallback: agent says 'I'll pull the latest signal' → calls A2A → reads back top 3 names.

Gotchas

Voiceflow API Blocks have a 30-second timeout, our A2A typically responds in <2s but cold-start can hit 5-10s; keep request volume reasonable.
If you embed in a voice agent, add a Speak Block that says 'one moment, pulling live data' before the API Block, UX without it feels like dead air.
Voiceflow's flow versioning treats Function code as project-scoped; if you fork the project, refactor Functions to a shared module so updates propagate.

When to pick which path

Because Voiceflow currently lacks a native MCP client, your two options are the custom tool below (a thin JSON-RPC wrapper you register once) or switching the session to an MCP-capable host when you need the richer tool surface. For scheduled jobs and pipelines, the raw endpoint is usually the sturdier dependency: no client versioning to track.

5example prompts are listed under "What you can ask" below, and the gotchas section covers the 3 known failure modes Voiceflow users hit with this endpoint. If a prompt fails, check the gotchas first: most misses are shape mismatches, not endpoint outages.

References

Try it without setup

The interactive playground lets you send live JSON-RPC requests against the A2A endpoint with no install, no auth. Pick a skill, hit send, see the response.

Full launch story: I made my VC deal flow callable by Claude.