Asmbly Neon Integrations
In attempts to further simplify our administrative operations so that we can focus on making cool stuff rather than route work, we're working to integrate our member management software - NeonCRM - with all our other systems. Completed scripts ready to set for automation are saved in the root directory. Scripts in /examples are work in progress.
Neon API docs
How to contribute:
First, thanks for collaborating! If you are part of the organization, please create a branch to work then submit a pull request to main. If you are outside the organization, we still welcome your collaboration! Just fork the repo, then submit a pull request.
NOTE: You will need to create a separate file config.py with API keys (this will be ignored by git). Variables used are
D_APIkey, D_APIuser, G_password , G_user, N_APIkey, N_APIuser, O_APIkey, O_APIuser, and S_APIkey.
Systems to integrate:
Discourse
- Forum for member discussion
- API docs
GETcalls only require API key and API user in headersPOSTcalls require API key, API user, and content-type in the headers- Neon -> Discourse to update Discourse group membership
Smartwaiver - DEPRECATING
We are switching to signNow and will use their Zapier Neon CRM integration.
See SWintegration.py.
Needs to be set to run on a schedule. Could be a monitored cron job or something else (AWS Lambda?).
- System for member agreement & waiver forms
- API docs
- To authenticate, add 'sw-api-key' to the headers with the API key.
- Smartwaiver -> Neon to update WaiverCompleted custom field in Neon
- Smartwaiver -
GET/v4/waivers - Neon -
PATCH/accounts/{id}
- Smartwaiver -
OpenPath
- Used for access into the space
Skedda
- Scheduling system for booking time at the space
- Checked with CSM about API, they have integrations through Zapier, but no direct access endpoint
- We will need to explore SSO/SAML options for user management (info here)
About this repo
This is an open-source project for Asmbly Makerspace, Inc. 501(c)3. Keep any API tokens or other private information should be stored in the /private directory or config.py both of which are ignored by git. If you are interested in working on this project with us, please reach out to it@asmbly.org.
Metadata
Release files for asmbly-neon-integrations 0.1.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| asmbly_neon_integrations-0.1.13.tar.gz | 25.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asmbly_neon_integrations-0.1.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.7 kB
Release files / asmbly_neon_integrations-0.1.13.tar.gz
| Download URL | asmbly_neon_integrations-0.1.13.tar.gz |
|---|---|
| Size | 25.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b433275dd82dd219be42f9be464daa055d2791d3f68aa100afb4f4832f15776a
|
|
BLAKE2b-256 checksum How to use checksums |
b81223f30edaec1695c17fb6f3113ba343e46886e70330c8fca501e37e9408ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.2 CPython/3.11.5 Darwin/23.2.0
|
Release files / asmbly_neon_integrations-0.1.13-py3-none-any.whl
| Download URL | asmbly_neon_integrations-0.1.13-py3-none-any.whl |
|---|---|
| Size | 30.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
06a2c273cdfe67e4ea4f4c61d9249e45ce65ba847c84a377ad97118021195ae1
|
|
BLAKE2b-256 checksum How to use checksums |
ddceae6636b0eb633f340154d5df9e587370f9a1c354e3cd0c5aaed1d037d562
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.2 CPython/3.11.5 Darwin/23.2.0
|