Over the last few weeks, there’s been a bit of excitement in the world of Church Community Builder, also affectionately known as CCB.
I use “excitement” loosely as many churches using CCB’s API were informed about CCB implementing a new per-minute rate limiting policy in addition to its per-day allotment of 10,000 calls per day — which they hope to retire sooner rather than later, yet it’ll remain in place for now.
As of August 20th, this new rate limiting strategy aims to restrict how many times per minute an API user can access an individual API Service — noted in New API Rate Limiting documentation.
So, what does this truly mean to you, and more importantly, how does this new strategy impact developed applications and environments using CCB’s API? 🤔 Read This Tutorial
Last week, I showed you how to create a Queue overdue list of persons report.
This week, we’re going to work with the same tutorial, yet extend upon the base functionality you developed thus far.
As with any tutorial we extend upon, I’m not going to cover the nitty-gritty details of the previous tutorial. You’ll have a bit of reading and review for areas you find to be challenging.
That said, today’s tutorial focuses on having a Queue overdue persons report emailed to you using Church Community Builder’s API service.
You would right to think that you can already do such reporting by using the existing web front-end interface as provided by CCB.
But what if you wanted to access the data programmatically using a 3rd-party system?
Well, this is where last week’s and today’s tutorials come quite in handy. Let’s get started.Read This Tutorial
Geez, just re-reading the title makes me (and probably you too!) cringe at the thought of using the Church Community Builder API to automate processes, queues and attendance reporting into a repeatable dynamic action.
That’s a thought and mouthful to repeat.
Well, it’s been a fast moving week for me, and I’ve been a bit slow delivering today’s tutorial.
In fact, I wish I had finished and posted it earlier than now, and let me explain why.
As most of you know, I’m a member of and volunteer at Mosaic Church in Austin, Texas. My primary responsibility outside of discipling, ministering and leading is being the point of contact for our Foundation and Membership Classes, and the Membership Process in its entirety.
We recently had our latest Foundations Class end this past Sunday. As I was attempting to MANUALLY figure out who attended 4 or more classes and completed Membership Class, I was reminded how much I needed today’s tutorial.
It is possible to manually create reports using the CCB front-end interface and achieve the task.
However, I rarely have time to lose, and I like being able to setup the use of repeatable and dynamic automation using cron jobs. Read This Tutorial
We’re back with this week’s tutorial that will build on and combine the following tutorials:
- How to retrieve a list of group participants
- Retrieving individual activity attendance
- How to automate using cron jobs
- Creating a reusable function for CCB API calls
I’ll discuss and show you how to combine tutorials to *automagically* export data from CCB, using the CCB API of course, into an Excel spreadsheet.
I won’t cover the automation portion in detail, but you can review the third bulleted tutorial above for that information. Let’s get started.Read This Tutorial
Before we begin, here’s a quick disclaimer to keep in mind… it is against Mailchimp’s terms of service to send transactional personalized emails. Because of this, Mailchimp allows for transactional personalized emails to be sent via the service Mandrill.
You may be wondering, “What exactly are transactional personalized emails?” Emails like password reminders, order confirmations, receipts, and personalized notifications qualify as transactional emails because they contain personalized information.
Building on the Birthday Emailer Tutorial
Remember the birthday emailer tutorial? Yes, it too qualifies as a transactional email. Now you may be thinking, “Why would I send the birthday emailer when I have existing sending capability?” Great question!
In the birthday emailer tutorial, you’re using good ole’ SMTP and the built-in PHP mailer functionality to send email. The catch to sending email using PHP mailer is that you must have SMTP enabled and properly setup.
Not to mention that your web/email host could block you from sending such messages in bulk. So knowing this, you now have a second option for sending messages using Mailchimp and Mandrill.