Skip to content

[FEATURE] Replace Zapier with a Google Apps Script in the ROR Curation Request Form #365

@adambuttrick

Description

@adambuttrick

Describe the problem you would like to solve

The ROR curation form currently uses Zapier to create GitHub issues from form submissions. Zapier adds an ongoing cost and an external dependency that can break in various ways. The same functionality can be recreated using a Google Apps Script attached to the form, which posts issues to GitHub via the API on each submission.

Describe the solution you'd like
Replace Zapier with a Google Apps Script attached to the ROR curation form by doing the following:

  1. Attach a Google Apps Script to the ROR curation form that maps form field IDs to the issue fields, formats as GitHub issue markdown, with permissions to create issues in ror-updates with a fine-grained token
  2. Configure a trigger on the script set to run onFormSubmit on the "From form / On form submit" event.
  3. Deprecate and remove Zapier once the Apps Script is verified working.

Who would benefit from this feature?
ROR team members who manage the curation form and process incoming requests.

Metadata

Metadata

Assignees

No one assigned

    Labels

    curationManaging registry data and registry updatesfeatureTotally new functionality that does not exist in ROR currently

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions