Trying to understand the concept here. It feels sort of like ifttt or zapier. But different, because the "UI" for creating integrations is spread out on to the 3rd party sites (Github, Airtable, etc)...by injecting the UI with a chrome plugin. As opposed to a central administrative UI.
Is that roughly correct?
Edit: Ahh, not just background integration, but also a greasemonkey like ability to tweak the 3rd party sites as well, right?
This is for building add-ons for GitHub, Asana, Trello, Airtable, Pivotal Tracker, and other productivity apps. And they don't break because they cleanly use that app's API.
The primary features are meant to make API development much better:
- Sign in with X instead of setting up OAuth flows or auth.
- Webhooks are built in, so you don't need a server to catch.
- API docs autocomplete. No need to dig through them.
- It's Serverless. Deploy your add-on on save.
It's inspired by Google Apps Script, the platform that powers all Google Docs add-ons. Hence less like Greasemonkey in that it uses real APIs under the hood, and less like Zapier in that it's for building add-ons instead of event pipelines.
Seems like you rely on the chrome extension to initiate the script? I.e. for the mail merge from airtable, you figure out which page the users is on to know which table to merge from correct?
If so, might I suggest inboxsdk.com for help with your extension dealing with Gmail.
You're right -- since these apps don't (yet) embed our SDK in to their site, we need to get the current state (eg current page, selected table, etc) from the Chrome Extension. But our goal is to provide entire entire extensibility platform in an embeddable JS snippet, so hopefully that won't be the case long.
Unfortuantely it might be difficult to convince Google to include your script inside their apps :)
Other than our InboxSDK, you could also look into building a gmail addon and having your users install that, but it would be another install in addition to your chrome extension.
Good question. You'll need to trust the company behind this, and make sure the scopes they're requesting are reasonable. Similar to any other app you use that asks you to "sign in with x". Luckily here, the company behind this (https://www.blockspring.com) is used by thousands of businesses, so a safe bet.
- when a trello card is due send me a message on Facebook to tell me to stop watching memes.
- when someone opens an issue on GitHub with a specific keyword send me a slack notification.
- when i get an email from someone (like a client) requesting a quote, open a new card in Trello in the prospective clients board
Any chance to get LinkedIn support?