A2A INTEGRATION · CUSTOM TOOL

Use GitDealFlow A2A with Inngest

Durable workflow runner with AI Kit. Builders running long-running, retryable agent workflows in production.

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

Inngest's AgentKit gives you durable, retryable agent workflows. Wrap our A2A endpoint as an Inngest function and chain it into multi-step flows that survive crashes and retries, perfect for 'every Monday at 9am, pull trending and email the top 5 to subscribers' type loops.

Endpoint facts for Inngest 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 Inngest path	Inngest has no native MCP client yet, so the custom-tool path below (a thin JSON-RPC call) is the way in.

Install

npm install inngest @inngest/agent-kit

Inngest function calling A2A

import { Inngest } from "inngest";

const inngest = new Inngest({ id: "vc-scout" });

export const weeklyDigest = inngest.createFunction(
  { id: "weekly-digest", name: "Weekly VC digest" },
  { cron: "0 9 * * 1" }, // Monday 9am
  async ({ step }) => {
    const trending = await step.fetch("https://signals.gitdealflow.com/api/a2a", {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify({
        jsonrpc: "2.0", id: 1, method: "message/send",
        params: { message: { role: "user", parts: [
          { kind: "data", data: { skill: "get_trending_startups" } },
        ]}},
      }),
    });
    const data = (await trending.json()).result.artifacts[0].parts[0].data;

    await step.run("email-subscribers", async () => {
      // ...your email send here...
      return { sent: data.startups.length };
    });
  },
);

What you can ask

Cron-triggered Monday digest of trending startups.
Event-triggered workflow: when a tracked org breaks out, email + open a CRM task.
Multi-step: scout → enrich (Crunchbase) → verify (Wellfound) → memo (LLM step) → email.
Retryable batch: 'enrich 50 startups' with automatic backoff on 429s.

Gotchas

step.fetch retries automatically on 5xx, our endpoint returns 200 with JSON-RPC error envelopes, so check `result` vs `error` in the response, not the HTTP status.
AgentKit's stateful agents persist context across steps; pass only the data fields you need to the next step to keep state size sane.

When to pick which path

Because Inngest 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.

4example prompts are listed under "What you can ask" below, and the gotchas section covers the 2 known failure modes Inngest 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.