asmbly-neon-integrations 0.1.1

Various convenience functions and scripts for managing integrations at Asmbly Makerspace.

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
• GET calls only require API key and API user in headers
• POST calls 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
    • https://api.smartwaiver.com/docs/v4/#api-Search-Search
  • Neon - PATCH /accounts/{id}
    • https://api.smartwaiver.com/docs/v4/#api-Waivers-WaiverList
      
      

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 [e-mail].