Show HN: I built developer tooling for the Airtable API that I needed (airwalker.io)
As a software engineer, I've experienced firsthand the challenges of working with the Airtable API.
As more non-technical users began using the platform in our growing business, the need for engineering to automate processes and sync data into Airtable grew. However, keeping track of process failures and ensuring that no unresolved failures slipped by was difficult and required significant effort.
That's why I created Airwalker, a toolkit that improves the reliability of processes using the Airtable API and helps you correct issues quickly and with minimal effort.
Here are some of the features Airwalker offers:
* Base schema timeline
* Request/response logging
* Edit & replay
* Custom automatically maintained TypeScript types
Airwalker is free to use right now, and I welcome any feedback or suggestions.
29 comments
[ 0.27 ms ] story [ 72.0 ms ] threadThe API is indeed a little bit clunky, but it works fine.
I've had to write my own Airtable handler (e.g.: API response schema validation and type translation) codes for all my projects where I've used it, maybe this could actually be a great unified solution.
Edit: The Superinverse logo is nice.
I've also thought about additional an additional layer of validation & type transformation, one for roadmap.
I like the Superinverse logo too!
Thanks so much for sharing this!
Thank you for sharing, feel free to reach out if I can help out.
I was a little taken aback when I went to sign up for the free trial and got hit by a Stripe checkout, though. Yes, checkout was for £0.00, but still, it was enough to make me close the tab at that point. This project is interesting but probably still a long shot for our workflows, so that (admittedly fairly low) barrier was a blocker.
Best of luck!
[1] https://2022.demuxed.com (last year's conference site)
Happy to talk more about your workflows if you'd like, but I appreciate you might already be able to tell whether Airwalker would be a fit or not.
An overview of the supported SQL syntax is here:
https://blaze.today/datablaze/docs/bsql/
No joins yet between tables yet, but they are planned. (You can use lookup fields to achieve them to some extent, but that requires planning ahead and is limited).
I tried to open your Terms and Privacy Policy pages but both are spitting a 400 error after timing out.
I'm not able to reproduce this currently, maybe it's fine on your end now too?
For interactivity I wrote some custom JS, I think it's similar to libraries like https://htmx.org or https://turbo.hotwired.dev, this stuff is inside the application though.
Let me know if there's anything you were particularly interested in knowing.
To be honest my curiosity was more of an engineering itch, what kind of setup would exhibit the failure mode I observed (a specific static route timing out).
Have you considered rendering HTML pages statically to avoid situations like this?
(By the way don’t let this conversation distract you from focusing on your product, your website is already excellent! And I appreciate you taking the time to reply :)
I should mention that the terms are fetched via an external API, I think that API failing temporarily caused the issue you were observing.
You’re right, static generation would have avoided the issue. Alternatively, I could be caching the response for a period. I’ve also got HAProxy in front of the application servers, but haven’t explored it’s caching capabilities.
For 'goksan, I'm curious what kind of research you did on the customer base for this, and how you thought through pricing? It feels attractive to me, but curious if there's more rigor involved there.
The API still a subset of the Airtable API for the moment to avoid requiring rewrites of existing integrations. I do plan to expand the API in the future to enable novel features.
Most of my research is in talking to other engineers using Airtable, admittedly none used Airtable as widely as we did at my last job.
I want to deliver the best possible experience for Airtable API integrations, and I believe pricing in the speculated range is necessary to sustain that focus. It's something I'm still thinking about.
Moving out of Airtable and replicating all of it's goodies is a tricky and expensive task, I'd like to help customers avoid that where possible, or delay it at the very least.
Hope everything is going great out there :)
I haven't thought about it too much personally, I think it'd be super useful though!