# Church Tech Stack Detector – ChMS, Giving & Livestream (`dbsimpjr28/church-tech-stack`) Actor

Find which church management software, online giving, livestream and website platforms a church uses (Planning Center, Pushpay, Tithe.ly, Subsplash, Resi, Nucleus and 90+ more), plus emails, phones, socials, service times and sales-ready lead flags.

- **URL**: https://apify.com/dbsimpjr28/church-tech-stack.md
- **Developed by:** [David Simpkins Jr.](https://apify.com/dbsimpjr28) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 church website analyzeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Church Tech Stack Detector – ChMS, Online Giving & Livestream

Find out what software a church runs **before** you call them. Paste church websites (or a Google Maps dataset of churches) and get back their church management system, giving platform, livestream provider, website builder, church app, email tools, contacts, service times and a list of sales-ready gaps.

Built for:

- **Church software companies:** find churches on a competitor (e.g. "uses Realm, no app") or with no online giving at all.
- **Church website and media agencies:** find churches with outdated sites, no HTTPS, no livestream or no mobile layout.
- **Denominations, networks and researchers:** measure adoption of giving and streaming across a region.

### What it detects (100+ products)

| Category | Examples |
|---|---|
| Church management (ChMS) | Planning Center, Realm (ACS), Breeze, Rock RMS, MinistryPlatform, CCB/Pushpay ChMS, Elvanto, Fellowship One, Shelby, ChurchTrac, ParishSOFT, Churchteams, Faithlife |
| Online giving | Pushpay, Tithe.ly, Givelify, Church Center Giving, Vanco, SecureGive, Realm/Breeze/Rock giving, OSV, WeShare, Faith Direct, Donorbox, Givebutter, PayPal, Venmo, Cash App |
| Livestream | YouTube Live/embeds, Facebook Live, Vimeo, BoxCast, Resi, Church Online Platform, StreamSpot, Dacast, Castr |
| Website platform | Nucleus, Clover, Ekklesia 360, Church Plant Media, Sharefaith, Finalweb, The Church Co, eCatholic, Diocesan, LPi, SnapPages, Squarespace, Wix, WordPress, Webflow, Duda… |
| Church app & media | Subsplash, The Church App, SermonAudio, RightNow Media, FORMED, podcasts |
| Email & text | Mailchimp, Constant Contact, Flocknote, Text In Church, Clearstream, Gloo |
| Other | KidCheck, Eventbrite, Jotform, chat widgets, Google Analytics/Tag Manager, Meta Pixel, accessibility overlays |

It scans the homepage plus the church's **give, watch, visit, staff and contact** pages (including subdomains like `give.church.org`), so it catches tools that only appear one click deep.

### Lead flags

Every church gets a `leadFlags` list so you can filter straight to prospects:

`no-online-giving` · `no-livestream-detected` · `no-chms-detected` · `outdated-copyright` · `no-https` · `not-mobile-friendly` · `no-public-email`

Set **Only output churches with these gaps** to get only the churches you can sell to.

### Input

- **Church websites:** URLs or bare domains.
- **Or an Apify dataset ID:** for example, the output of a Google Maps scraper run for "churches in Dallas, TX". Each Maps row is carried through in `source`, so you keep the name, address and rating.

### Output example

```json
{
  "churchName": "Example Community Church",
  "domain": "examplechurch.org",
  "chms": ["Planning Center"],
  "givingPlatforms": ["Church Center Giving (Planning Center)"],
  "streamingPlatforms": ["Church Online Platform", "YouTube (embedded video / live)"],
  "websitePlatform": "Squarespace",
  "churchApp": [],
  "communicationTools": [],
  "emails": ["hello@examplechurch.org"],
  "phones": ["(555) 010-0123"],
  "socials": { "facebook": "https://www.facebook.com/…", "instagram": "https://www.instagram.com/…", "youtube": "https://www.youtube.com/@…" },
  "serviceTimes": ["Sundays at 10:00am"],
  "pages": { "give": "https://examplechurch.org/give", "watch": "https://examplechurch.org/watch" },
  "copyrightYear": 2026,
  "https": true,
  "mobileFriendly": true,
  "leadFlags": [],
  "status": "ok"
}
```

### Pricing

You pay **per church analyzed**. Sites that are down, don't exist or block the request are listed with an `error` and are **free**. There's no proxy cost for most sites.

### Tips

- About 1,000 churches take a few minutes with the default 10 parallel sites.
- A few very large churches build their sites entirely in JavaScript and load giving widgets after the page renders. Those may show fewer detections. Most small and mid-size church sites are fully detectable.
- If a site returns `http-403`, run it again with Apify Proxy turned on.

Questions or a vendor we should detect? Open an issue on the Actor page. We usually reply the same day.

# Actor input Schema

## `startUrls` (type: `array`):

Church website URLs or bare domains (e.g. elevationchurch.org).

## `datasetId` (type: `string`):

Analyze every website in an existing dataset, e.g. the output of a Google Maps scraper run for 'churches in Dallas'.

## `websiteField` (type: `string`):

Column holding the URL. Google Maps scrapers use 'website'.

## `maxSites` (type: `integer`):

Stop after this many websites.

## `maxPagesPerSite` (type: `integer`):

Homepage plus the give / watch / visit / staff / contact pages. More pages = more detections.

## `onlyWithLeadFlags` (type: `array`):

Leave empty for all. Useful for sales lists, e.g. only churches with no online giving.

## `includeEvidence` (type: `boolean`):

Adds the matched pattern and page for each technology.

## `maxConcurrency` (type: `integer`):

How many sites to scan at the same time.

## `proxyConfiguration` (type: `object`):

Not needed for most church sites.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.redeemerpgh.org/"
    },
    {
      "url": "https://waverlychurch.org/"
    }
  ],
  "websiteField": "website",
  "maxSites": 1000,
  "maxPagesPerSite": 4,
  "includeEvidence": false,
  "maxConcurrency": 10,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All items the run produced, in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        {
            "url": "https://www.redeemerpgh.org/"
        },
        {
            "url": "https://waverlychurch.org/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dbsimpjr28/church-tech-stack").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": [
        { "url": "https://www.redeemerpgh.org/" },
        { "url": "https://waverlychurch.org/" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("dbsimpjr28/church-tech-stack").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://www.redeemerpgh.org/"
    },
    {
      "url": "https://waverlychurch.org/"
    }
  ]
}' |
apify call dbsimpjr28/church-tech-stack --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dbsimpjr28/church-tech-stack"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/2Fd4UlwRr9OiiiywP/builds/EyEKl8pBRJpOJmQH5/openapi.json