datafire / integrations Goto Github PK

View Code? Open in Web Editor NEW

134.0 134.0 52.0 133.52 MB

Integration registry for DataFire

License: MIT License

JavaScript 99.57% Shell 0.15% HTML 0.28% CSS 0.01%

integrations's Introduction

DataFire

DataFire is an open source framework for building and integrating APIs. It provides over 1000 integrations, including:

AWS • Azure • MongoDB • Slack • GitHub • Twilio • Trello • Square • Google Sheets • Gmail • Heroku

Each integration provides a set of composable actions. New actions can be built by combining existing actions, JavaScript, and external libraries. They are driven by JavaScript Promises, and can be triggered by a URL, on a schedule, or manually.

Want more? DataFire.io provides a simple interface for building, managing, and hosting DataFire projects.

Installation

Be sure to install DataFire both globally and as a project dependency.

npm install -g datafire
npm install --save datafire

Documentation

The full documentation is available at docs.datafire.io

Sample Projects


Create an API backed by Google Sheets	Repo	Run on DataFire.io
E-mail yourself news headlines	Repo	Run on DataFire.io
Backend for a "Contact Us" form	Repo	Run on DataFire.io
Sync GitHub issues to a Trello board	Repo	Run on DataFire.io
Create a Spotify playlist from r/listentothis	Repo	Run on DataFire.io

Contributing

Contributions are welcome!

Getting Started

git clone https://github.com/DataFire/DataFire && cd DataFire
npm install

Tests are run with npm test and require ports 3333-3336 to be open.

integrations's People

Contributors

Stargazers

Watchers

integrations's Issues

Is this project still maintained?

Hi,

I am planning on working on a few integration modules for a project but some open PRs have been around for quite some time so I am wondering if this project is still active?

Thanks.

Mixpanel API

[ Basecamp3 ] Missing replies in inbox_forwards's endpoint

As described in the Basecamp API repository, it seems we have an option to request the replies from the inbox_forward endpoint. However, the current Basecamp integration doesn't have that feature implemented.

As comments for other records within Basecamp, it would be great to have those as well.

Can anyone provide some insight on the "context" argument in the methods?

As stated I have reviewed the code and the RFC and I guess I am confused on what the "context" is and how to utilize it?
caldav.listEvents({ "filename": "" }, **context**)

@datafire/mailchimp api version 1.3 is no more working.

should change mailchimp api version to 3.0
Or create new @datafire/mailchimp3

CCXT Cryptocurrency library

Redmine x Visual Studio Team Services

Hey Guys,
Unfortunately I do not understand anything about NODEJS and about this part of integrations, I was wondering if it would be possible to create the integration between Redmine and Visual studio team services.
Same as Zarpier's
https://zapier.com/zapbook/redmine/visual-studio-online/
Thanks :)

After latest changes to slack integration search.all is missing.

Optional fields in PivotalTracker

The pivotal api v5 allows you to add some attributes/associations to the response as GET parameters, you can see it here on the section named "Selecting Attributes to Include in Responses"

Currently the PivotalTracker integration doesn't allow you to do it. Is there a way to do it? I'll be glad to work on a pull request for it or whatever. I need a starting point though and be sure that my work will be integrated if it's worth it :)

How to create thumbnail of Wowza Videos?

Hi,

I am looking for creating the thumbnails for all the videos which we have uploaded on Wowza.
I also want to know can we save these thumbnails on our server end, if it is possible to create thumbnails with the plugin.
I found this source link ( https://www.wowza.com/docs/how-to-generate-thumbnail-images-of-live-streams ), but this code is in JAVA. which we are not familiar with.
Need to do the same with this module.
Let me know if this is available or not?
Or is there any other way rather having java.

Thanks,

Optionalize host for traccar integration

Build Error for @datafire/gisgraphy: Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

after i npm i -D @datafire/gisgraphy and build it using webpack, i got a series of warnings and errors:

WARNING in ../node_modules/require-main-filename/index.js 2:25-32
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ../node_modules/datafire/node_modules/yargs/yargs.js
@ ../node_modules/datafire/node_modules/yargs/index.js
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/node_modules/yargs/index.js 11:39-46
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/yamljs/lib/Yaml.js 78:43-50
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ../node_modules/datafire/src/commands/run.js
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/node_modules/yargs/yargs.js 342:33-40
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ../node_modules/datafire/node_modules/yargs/index.js
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/node_modules/yargs/yargs.js 498:71-78
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ../node_modules/datafire/node_modules/yargs/index.js
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/src/lib/action.js 50:17-56
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/src/lib/integration.js 52:11-33
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/src/lib/integration.js 57:11-36
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/src/lib/project.js 112:33-76
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/distribution/src/lib/action.js 54:18-57
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/distribution/src/lib/index.js
@ ../node_modules/datafire/distribution/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/distribution/src/lib/integration.js 52:11-33
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/distribution/src/lib/index.js
@ ../node_modules/datafire/distribution/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/distribution/src/lib/integration.js 57:11-36
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/distribution/src/lib/index.js
@ ../node_modules/datafire/distribution/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/express/lib/view.js 81:13-25
Critical dependency: the request of a dependency is an expression
@ ../node_modules/express/lib/application.js
@ ../node_modules/express/lib/express.js
@ ../node_modules/express/index.js
@ ../node_modules/datafire/src/lib/project-server.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/distribution/src/commands/integrate.js 57:40-96
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/distribution/src/commands/index.js
@ ../node_modules/datafire/distribution/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/distribution/src/commands/integrate.js 91:22-44
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/distribution/src/commands/index.js
@ ../node_modules/datafire/distribution/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/distribution/src/lib/project.js 117:33-76
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/distribution/src/lib/index.js
@ ../node_modules/datafire/distribution/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/node_modules/yargs-parser/index.js 444:21-48
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/node_modules/yargs/yargs.js
@ ../node_modules/datafire/node_modules/yargs/index.js
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/src/commands/integrate.js 55:19-75
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/src/commands/integrate.js 92:22-44
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/node_modules/ajv/lib/async.js 96:20-33
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/node_modules/ajv/lib/ajv.js
@ ../node_modules/datafire/src/util/ajv.js
@ ../node_modules/datafire/src/util/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/node_modules/ajv/lib/async.js 119:15-28
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/node_modules/ajv/lib/ajv.js
@ ../node_modules/datafire/src/util/ajv.js
@ ../node_modules/datafire/src/util/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/datafire/node_modules/ajv/lib/compile/index.js 13:21-34
Critical dependency: the request of a dependency is an expression
@ ../node_modules/datafire/node_modules/ajv/lib/ajv.js
@ ../node_modules/datafire/src/util/ajv.js
@ ../node_modules/datafire/src/util/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/yamljs/lib/Yaml.js 79:6-24
require.extensions is not supported by webpack. Use a loader instead.
@ ../node_modules/datafire/src/commands/run.js 3:13-30
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/yamljs/lib/Yaml.js 80:13-31
require.extensions is not supported by webpack. Use a loader instead.
@ ../node_modules/datafire/src/commands/run.js 3:13-30
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

WARNING in ../node_modules/yamljs/lib/Yaml.js 78:62-80
require.extensions is not supported by webpack. Use a loader instead.
@ ../node_modules/datafire/src/commands/run.js 3:13-30
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/datafire/distribution/src/commands/integrate.js
Module not found: Error: Can't resolve 'child_process' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/datafire/distribution/src/commands'
@ ../node_modules/datafire/distribution/src/commands/integrate.js 6:11-35
@ ../node_modules/datafire/distribution/src/commands/index.js
@ ../node_modules/datafire/distribution/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/datafire/node_modules/os-locale/index.js
Module not found: Error: Can't resolve 'child_process' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/datafire/node_modules/os-locale'
@ ../node_modules/datafire/node_modules/os-locale/index.js 2:19-43
@ ../node_modules/datafire/node_modules/yargs/yargs.js
@ ../node_modules/datafire/node_modules/yargs/index.js
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/datafire/src/commands/integrate.js
Module not found: Error: Can't resolve 'child_process' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/datafire/src/commands'
@ ../node_modules/datafire/src/commands/integrate.js 4:13-37
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/express/lib/request.js
Module not found: Error: Can't resolve 'net' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/express/lib'
@ ../node_modules/express/lib/request.js 18:11-25
@ ../node_modules/express/lib/express.js
@ ../node_modules/express/index.js
@ ../node_modules/datafire/src/lib/project-server.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/forever-agent/index.js
Module not found: Error: Can't resolve 'net' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/forever-agent'
@ ../node_modules/forever-agent/index.js 6:10-24
@ ../node_modules/request/request.js
@ ../node_modules/request/index.js
@ ../node_modules/datafire/src/commands/integrate.js
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/tough-cookie/lib/cookie.js
Module not found: Error: Can't resolve 'net' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/tough-cookie/lib'
@ ../node_modules/tough-cookie/lib/cookie.js 32:10-24
@ ../node_modules/request/lib/cookies.js
@ ../node_modules/request/index.js
@ ../node_modules/datafire/src/commands/integrate.js
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/tunnel-agent/index.js
Module not found: Error: Can't resolve 'net' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/tunnel-agent'
@ ../node_modules/tunnel-agent/index.js 3:10-24
@ ../node_modules/request/lib/tunnel.js
@ ../node_modules/request/request.js
@ ../node_modules/request/index.js
@ ../node_modules/datafire/src/commands/integrate.js
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/spdx-expression-parse/scan.js
Module not found: Error: Can't resolve 'spdx-exceptions' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/spdx-expression-parse'
@ ../node_modules/spdx-expression-parse/scan.js 6:17-43
@ ../node_modules/spdx-expression-parse/index.js
@ ../node_modules/validate-npm-package-license/index.js
@ ../node_modules/normalize-package-data/lib/fixer.js
@ ../node_modules/normalize-package-data/lib/normalize.js
@ ../node_modules/datafire/node_modules/read-pkg/index.js
@ ../node_modules/datafire/node_modules/read-pkg-up/index.js
@ ../node_modules/datafire/node_modules/yargs/yargs.js
@ ../node_modules/datafire/node_modules/yargs/index.js
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/spdx-correct/index.js
Module not found: Error: Can't resolve 'spdx-license-ids' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/spdx-correct'
@ ../node_modules/spdx-correct/index.js 17:21-48
@ ../node_modules/validate-npm-package-license/index.js
@ ../node_modules/normalize-package-data/lib/fixer.js
@ ../node_modules/normalize-package-data/lib/normalize.js
@ ../node_modules/datafire/node_modules/read-pkg/index.js
@ ../node_modules/datafire/node_modules/read-pkg-up/index.js
@ ../node_modules/datafire/node_modules/yargs/yargs.js
@ ../node_modules/datafire/node_modules/yargs/index.js
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/spdx-expression-parse/scan.js
Module not found: Error: Can't resolve 'spdx-license-ids' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/spdx-expression-parse'
@ ../node_modules/spdx-expression-parse/scan.js 4:10-37
@ ../node_modules/spdx-expression-parse/index.js
@ ../node_modules/validate-npm-package-license/index.js
@ ../node_modules/normalize-package-data/lib/fixer.js
@ ../node_modules/normalize-package-data/lib/normalize.js
@ ../node_modules/datafire/node_modules/read-pkg/index.js
@ ../node_modules/datafire/node_modules/read-pkg-up/index.js
@ ../node_modules/datafire/node_modules/yargs/yargs.js
@ ../node_modules/datafire/node_modules/yargs/index.js
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/spdx-expression-parse/scan.js
Module not found: Error: Can't resolve 'spdx-license-ids/deprecated' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/spdx-expression-parse'
@ ../node_modules/spdx-expression-parse/scan.js 5:10-48
@ ../node_modules/spdx-expression-parse/index.js
@ ../node_modules/validate-npm-package-license/index.js
@ ../node_modules/normalize-package-data/lib/fixer.js
@ ../node_modules/normalize-package-data/lib/normalize.js
@ ../node_modules/datafire/node_modules/read-pkg/index.js
@ ../node_modules/datafire/node_modules/read-pkg-up/index.js
@ ../node_modules/datafire/node_modules/yargs/yargs.js
@ ../node_modules/datafire/node_modules/yargs/index.js
@ ../node_modules/datafire/src/lib/event.js
@ ../node_modules/datafire/src/lib/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/forever-agent/index.js
Module not found: Error: Can't resolve 'tls' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/forever-agent'
@ ../node_modules/forever-agent/index.js 7:10-24
@ ../node_modules/request/request.js
@ ../node_modules/request/index.js
@ ../node_modules/datafire/src/commands/integrate.js
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

ERROR in ../node_modules/tunnel-agent/index.js
Module not found: Error: Can't resolve 'tls' in '/home/[user_name]/dev/[project_folder]_admin/node_modules/tunnel-agent'
@ ../node_modules/tunnel-agent/index.js 4:10-24
@ ../node_modules/request/lib/tunnel.js
@ ../node_modules/request/request.js
@ ../node_modules/request/index.js
@ ../node_modules/datafire/src/commands/integrate.js
@ ../node_modules/datafire/src/commands/index.js
@ ../node_modules/datafire/src/index.js
@ ../node_modules/datafire/src/entry.js
@ ../node_modules/@datafire/gisgraphy/index.js
@ ./[project_folder]/modules/app/gisgraphy.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/epic.jsx
@ ./[project_folder]/modules/gisgraphy/parse_address/index.jsx
@ ./[project_folder]/modules/app/epic.jsx
@ ./[project_folder]/modules/app/store.jsx
@ ./[project_folder]/index.jsx
@ multi ./[project_folder]/index.jsx

i was just searching for a npm lib of gisgraphy to test the api in my development so in the long run i might setup my own server, but until then, is there any other public api for gisgraphy that you know?

thank you.

ZenHub API

https://www.npmjs.com/package/zenhub-api

https://github.com/ZenHubIO/API

Integration with outlook calendar

SMTP integration friendly names

Hi! I'm currently using datafire to use some of your awesome integrations. When using the SMTP integration however, it seems there's no way to send friendly names on the to or the from fields. I've seen that Datafire's SMTP integration uses Nodemailer's SMTP Connection as its underlying technology, which apparently doesn't allow this. Maybe this integration could use Nodemailer (instead of SMTP Connection) as defined here: https://nodemailer.com/smtp/envelope/ .

What's expected:
Using the following:

let smtp = require('@datafire/smtp').create({
  host: "",
  port: "",
  username: "",
  password: ""
});

smtp.send({
  "from": "Example Sender <[email protected]>",
  "to": []
}).then(data => {
  console.log(data);
});

It should allow me to send an email with "Example Sender" as friendly name and "[email protected]" as its email.

What happens:

We get an "Invalid sender" error.

If you guys agree, I could issue a PR with this since it could be something useful.

Please merge pull request for MailboxValidator integration

We have created a pull request for the MailboxValidator integration. Please accept the request.

Integration with JIRA requires username and password

In your code, you mention to activate JIRA, one should instantiate using username, and password to be sent to those calls, can we do without it? Just plain old, oauth token?

Integration for Vtiger (opensource) and GravityForms

Basically what the title says. Is that difficult to do or...?

square-connect: ListCatalog failing due to example data

ListCatalog in Square-connect is pulling example data from the API, which causes schema collisions.

Calculate HMAC signatures for AWS integrations

AWS requests need to be signed. Right now AWS creds ask for an HMAC signature, but instead we should ask for accessKeyId and secretAccessKey, and calculate HMAC automatically.

http://czak.pl/2015/09/15/s3-rest-api-with-curl.html

http://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html

Can't connect WaveCell API

I am trying to send a single SMS but every time I try to send one, console responds failed with status code 401.

I believe that I do not understand this part of code:
let wavecell = require('@datafire/wavecell').create({ username: "", password: "" });

I don't what to put here. Inputting the registered username and password doesn't seem to work.

Target Process API

'context' var in basecamp3 api

Hi there! first off thanks for providing this package! I'm running the script you provided on the readme.md page of https://www.npmjs.com/package/@datafire/basecamp

but running any of the GET requests, such as

let basecamp = require('@datafire/basecamp').create({
  access_token: "",
  refresh_token: "",
  client_id: "REDACTED",
  client_secret: "REDACTED",
  redirect_uri: "REDACTED"
  ApiKeyAuth: "",
  account_id: "REDACTED"
});
 
basecamp.projects.json.post({}).then(data => {
  console.log(data);
});

throws the error:

ReferenceError: context is not defined
    at Object.<anonymous> (/Users/mp/makedoc/basecamp/basecamp.js:17:4)
    at Module._compile (internal/modules/cjs/loader.js:702:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
    at Module.load (internal/modules/cjs/loader.js:612:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
    at Function.Module._load (internal/modules/cjs/loader.js:543:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:744:10)
    at startup (internal/bootstrap/node.js:238:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:572:3)

basecamp3 api pagination

Hi There,

When requesting data from my basecamp3 account, I receive only 15 entries per JSON response. I understand this is due to basecamp's pagination rule. However, how do I ensure I receive all 'pages' from BC when using the @datafire/basecamp nodejs package?

How to generate openAPI specs

I was recently got curious about open APIs. 1. How did one can generate the open API specs even if the integration service companies didn't provide one? 2. How can one generate an open API spec from REST APIs if no other info is available other than documentation? Thank you.

specify url cache duration time in DataFire.yml for endpoint

Just an idea:

# DataFire.yml
paths:
  /hello:
    get:
      action: ./function/hello
      cache: 5

Many times i find myself caching endpoint responses to prevent expense async calls / speed up responses.
I usually use this middleware module cache.js:

var mcache = require('memory-cache');

// usage: 
//   var cache = require('cache')
//   app.get("/foo/bar*", cache(5) ) // cache 5 seconds
 
module.exports = (duration) => {
  return (req, res, next) => {
    let key = JSON.stringify({method:req.method, url:req.url, query:req.query, body:req.body, headers:req.headers })
    let cachedBody = mcache.get(key)
    if (cachedBody) {
      res.header(cachedBody.headers)
      res.send(cachedBody.body)
      return
    } else {
      res.sendResponse = res.send
      res.send = (body) => {
        var obj = {body:body, headers:res.header()._headers}
        mcache.put(key, obj, duration * 1000);
        res.sendResponse(body)
      }
      next()
    }
  }
}

Is this something which might be interesting to include in the datafire module?
It might also give the public datafire.io-server some headroom.

cheers

Slack integration "as_user" fails

Hi! I'm using @datafire/slack to send messages on behalf of a bot I've built on my own Slack team.

What happens
I'm using the integration's chat_postMessage action, with the following payload:

 {
    "channel": "@myUser",
    "text": "awesomeText"
  }

And it works. However, the mssage is sent through the "Slackbot" user on Slack. I wish to send this message on behalf of the App's bot. When trying this:

 {
   "as_user": true,
    "channel": "@myUser",
    "text": "awesomeText"
  }

 {
   "as_user": false,
    "channel": "@myUser",
    "text": "awesomeText"
  }

The request fails with:

_http_outgoing.js:642
    throw new TypeError('First argument must be a string or Buffer');
    ^

It seems as it's not letting the payload have a boolean value?

[ Basecamp3 ] Missing completed tasks in todo's endpoint

As per described on their API, Basecamp3 allows individuals to filter between completed and not completed task by passing a query parameter describing so. As of right now, by default Basecamp returns only the uncompleted tasks, so an additional query requiring the uncompleted ones are required.

It would probably be worth adding this option, as currently there's no easy way to consume the API to see completed tasks.

Gitlab "API V3 is no longer supported. Use API V4 instead."