Over the last 72 hours, we shipped seven SDKs and an n8n node for Spidra.
Before now, if you wanted to use Spidra in your project, you were likely hitting the API directly and wiring things up yourself.
That works, but it’s not how most people actually want to build. Everyone has their own stack, their own tools, and their own way of wiring things together.
So instead of expecting people to adjust to Spidra, we decided to make Spidra fit into how people already work.
That’s what this release is about.
What we shipped
We focused on making Spidra easier to use across different stacks. On the SDK side, we now have support for:
Each SDK wraps the same API, so you’re not learning something new in every language. You’re just using Spidra in a way that feels natural for your stack.
We also shipped an n8n node.
That makes it easier to plug Spidra into workflows without writing code. You can trigger scrapes, process results, and connect them to other tools directly inside your automation pipelines.
What’s next
We’re not done. We’re still in the middle of it.
Some SDKs are already being worked on, such as .NET, Java, Elixir, and Swift. They’re not far off, and the idea is the same as what we just shipped.
We’re also thinking beyond SDKs.
The n8n node was a first step into workflows, but it doesn’t stop there. We’re working towards deeper integrations with the tools people already use to automate things, such as MCP, Zapier, Make, and into the AI ecosystem with LangChain and LlamaIndex.
The direction is pretty simple. Whether you’re writing code, building automations, or wiring up agents, Spidra should just plug in without friction.
That’s what we’re continuing to push on.
