@agartha had a great idea about a IFTTT or Zapier integration for Graphcool: https://github.com/graphcool/feature-requests/issues/238 would love to find someone in the community to collaborate on this. Anyone interested? 🙂

@nilan me lol

I had thought zapier/ifttt were services used primarily by cms admins (wordpress/drupal/etc). If so, is that really a target audience for graphcool? If not, disregard.

Zapier and IFTTT are used to connect different systems. It's basically a big webhook system. Any system that produces relevant events for the outside world, or can consume relevant events from the outside world, can use it.

The benefit of this being that you can avoid manually interacting w/ the instagram api and instead use zap/ifttt?

Hmmm... I need to rethink my examples 🙂

@dk0r I have a very simple example that I encountered recently

Great example @nilan thank you

instead of digging through the Slack docs myself, I quickly setup a Zapier "Zap". A Zap has a "trigger" and something that "is triggered"

Ok. This sounds similar to agartha's example no? A graphcool mutation spawns a call back that interacts w/ the Slack api to post a slack notification?

in my case, the "trigger" was a simple HTTP POST, and the "is triggered" was a new message in my Slack channel

I see.

yea

So basically, zap/ifttt usage allows us to avoid direct interaction with various api's

that cost more time, because I needed to talk to the Slack API directly

I could see how that might be useful --pricing and usage (limited number of

zaps

) on those services also looks like a barrier to entry

I don't think there's a limited number of zaps, but a limited number of invocations

Both

it works well for my usage though, but it's a valid point that needs to be considered

There's a bit of layering going on. I'm building an app, based on Graphcool. If I want other apps to connect to my app and vice versa, I'd create a service on Zapier for my app, and let users setup Zaps to interact with it.

yeah --zap/ifttt integration would be interesting and open up graphcool to a whole new market. I just don't know how much that integration is worth

With Graphcool having it's own generic service on Zapier, I can directly use that to poll, query, mutate etc.

hmm

Well, the problem for Graphcool is that it's not an end-user product, but a back-end platform

right, but services like zap/ifttt kind of bridge that gap in a sense

Yes

which is why it could open up graphcool to a new market

so what would a new Graphcool integration offer?

queries can be used as trigger together with cron

ah is that something you can setup with Zapier already? the cron thing

Yes

sounds great

What is meant by

action-side

versus

trigger-side

?

Zaps, or IFTTT recipes, have a trigger side and an action side, the trigger initiates the action.