npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

planning-center-export

v0.8.0

Published

Export data from Planning Center

Downloads

11

Readme

Planning Center Export

Background

Simplifies the process of exporting data from Planning Center. While Planning Center does provide the ability to export data to files, this process must be done through the user interface and con be extremly time consuming. This package is designed to support automation of data extraction.

The inability to simply and reliably extract data from Planning Center for use in a data warehouse was the initial reason for the creation of this package.

Getting Started

Installing the package

terminal

npm install planning-center-export

Basic Example Export to JSON

.js

import { PlanningCenter, PlanningCenterEntities } from "planning-center-export"

// Configure output file and API keys
const groupsFilePath = "./groups.json";
const applicationId = process.env.PLANNING_CENTER_APPLICATION_ID;
const secret = process.env.PLANNING_CENTER_SECRET;

// Export the GROUPS data as JSON
const planningCenterConfig = { applicationId, secret };
const planningCenterExport = new PlanningCenter(planningCenterConfig);
const groupsResult = await planningCenterExport.export(PlanningCenterEntities.groups, groupsFilePath);

// Log the completion of the export
console.log(`${PlanningCenterEntities.groups} Export complete`)
console.log(`  ${groupsResult.totalCount} records written to: `, groupsFilePath);

Planning Center API keys

In order to make requests to the Planning Center API you must provide the API keys assigned to your Planning Center Account. Your API keys can be found here

Pass the Personal Access Tokens: Application ID and Secret pass them into the PlanningCenterExport constructor. These keys will automatically be included for all requests to the API.

Key Security

The Application ID and Secret should NEVER BE STORED IN CODE OR CHECKED INTO A CODE REPOSITORY. Please ensure that you store them in a secure way such as system environment variables or a .env file. The example above uses a .env file to store the keys, and uses the dotenv npm package to access them.

.env

PLANNING_CENTER_APPLICATION_ID=a72490....9abh
PLANNING_CENTER_SECRET=576a284...e79g

.js

import dotenv from "dotenv";
const applicationId = process.env.PLANNING_CENTER_APPLICATION_ID;
const secret = process.env.PLANNING_CENTER_SECRET;
const planningCenterConfig = { applicationId, secret };
const planningCenterExport = new PlanningCenter(planningCenterConfig);