DataFire

Process and transfer data between APIs, databases, and more.

Reviews

Discussion

You need to become a Contributor to join the discussion - Find out how.
Bobby Brennan
Bobby BrennanMaker@bobby_lucybot
Hi! We built DataFire to help us get more out of the services we were already using. You can read more on medium.com about our motivation for building DataFire, or about how we're already using it. DataFire allows you to interact with any API via small snippets of JavaScript. You can schedule daemons to run every day, hour, or minute. We've already seen some creative ideas come to life, and we're excited to see what developers build with DataFire. If you're not a developer, you can still customize and run pre-built daemons. We've already added over 200 integrations, and have opened up the ability to add new APIs via Swagger, RAML, or API Blueprint. We even added a small Product Hunt integration last night! You can see it in action with the Product Hunt Alerts daemon We'd love to hear what integrations you'd like to see next, or how you'd use DataFire to get more value out of the web!
Ryan J A Murphy
Ryan J A Murphy@ryanjamurphy · Student?
@bobby_lucybot I love these kinds of tools, but am already pretty heavily into IFTTT and Zapier. Can I ask for a pitch on what DataFire can do differently from those two? (I can imagine some examples but I like to hear it from the creator!)
Bobby Brennan
Bobby BrennanMaker@bobby_lucybot
@ryanjamurphy I'm a Zapier user as well. I built DataFire because whenever I wanted to do something mildly complex, Zapier either couldn't support it, or I had to fight to express the logic of it inside Zapier's UI. I found myself wishing I could just write a few lines of code. My post on medium goes into some more detail, but here are the three major features that differentiate us: The ability to write code. While mapping data inside a pretty UI is approachable for spreadsheet-savvy professionals, there are some tasks that only code can solve, and many tasks that become unwieldy without it. The ability to call 3 or more APIs in one flow. So many usecases fall to the wayside by limiting users to two API calls. Maybe I don’t want to just blindly retweet any mention of my company - surely it’d be better to use an NLP API to make sure it has positive sentiment and no curse words first. Or maybe I’d like to aggregate usage metrics from Mixpanel and Mandrill before inserting a new lead into Salesforce. The ability to schedule or run on demand. Most existing services expect your job to run continuously - every 5 or 15 minutes depending how much you pay. But maybe some jobs only need to run daily, and others need to run every minute - with DataFire you only pay for what you need. I see it as a continuum: IFTTT is for consumers (e.g. Fitbit and Instagram recipes) Zapier is for professionals (e.g. spreadsheets and gmail) DataFire is for developers and startups (e.g. Salesforce, Heroku, MongoDB, MailChimp) There's obviously some cross-over - plenty of serious things to do with IFTTT and fun things to do with DataFire - but that's how I see us fitting in.
David Iwanow
David Iwanow@davidiwanow · Global SEO Manager @ Schibsted
@bobby_lucybot @bbrennan looks interesting Bobby but I don't see any support for Asana or Basecampe
Jeff Needles
Jeff Needles@jsneedles · Data @ Houseparty & Maker of Things
Like IFTTT for data & dev. ❤️