4 ms·
How do you square this: > You can’t share a Zapier integration universally. With then plugging Autocode? How is an Autocode integration any more universal tha
by ucarion 6y ago
How do you square this:
> You can’t share a Zapier integration universally.
With then plugging Autocode? How is an Autocode integration any more universal than a Zapier one?
Also, how are you building the code for the various integrations Autocode supports? Is there some underlying interlingua that you codegen from?
- keithwhor 6y agoI'll show you. Here's an example of an Autocode "integration," or something in our standard library. It's a Halo API I added for fun. You can use the gamertag "citizen kwho" to find me. https://autocode.com/lib/halo/mcc/ https://autocode.com/lib/halo/mcc/ As you can see from the code examples, you just talk to it via an API key and a standard calling convention. It's completely portable. Autocode makes it easier to manage your tokens, code, etc. but you could port this to any Node.js codebase or make an HTTP request from anywhere. We have universal Ruby and Python libraries, too, but they're a little outdated. (Small team, have had to stay focused on Node.js for now.) Edit: I'll mention that technically anybody can add to our stdlib. We do a lot of the work ourselves right now, but it's fundamentally an open platform. Also see other comment re: FunctionScript specification and how we add APIs to the stdlib. :)
- cdcarter 6y agoIs there a place we can see the source for that Halo API binding?
- keithwhor 6y agoNot specifically for that API. I'd have to spend some time cleaning it up to open source it. But we have a really simple API connector example you can fork [0]. :) [0] https://autocode.com/app/keith/connector-pokefusion/ https://autocode.com/app/keith/connector-pokefusion/