Create Automation Linking PlanningCenter and a Business LINE account using Make

Hire a Pro Hire Help
1

Project Title

Planning Center ↔ Make.com ↔ LINE Official Account Integration (API + Automation)

Project Overview

I am looking for an experienced automation / API integration specialist to build a reliable, production-ready integration between Planning Center, Make.com (Integromat), and a LINE Official Account.

This is a short, well-defined project with a clear architecture already designed. The work involves configuring Make scenarios, handling API keys, webhooks, and implementing both one-way and two-way messaging logic using the LINE Messaging API.

This is not a beginner project. You should be comfortable working with REST APIs, JSON payloads, webhooks, and Make’s advanced features (routers, iterators, filters, HTTP modules).

Scope of Work

The project has three main components:

1. Identity Linking (One-Time Registration Bot)

  • Build a Make scenario that listens to inbound LINE messages (webhook).

  • User sends their email address via LINE.

  • Scenario searches Planning Center People by email.

  • If found, store the user’s LINE User ID in a custom Planning Center Person field (“LINE User ID”).

  • Result: One-time linking of Planning Center person ↔ LINE user.

2. Weekly Reminder Automation (Outbound Messaging)

  • Scheduled Make scenario (e.g. weekly).

  • Fetch upcoming service plans from Planning Center.

  • Retrieve scheduled volunteers (excluding “Declined”).

  • For each person:

    • Check for a stored LINE User ID.

    • Send a LINE Push Message with dynamic content:

      • Name

      • Role / position

      • Service time

      • Planning Center plan link

  • Use LINE Messaging API (Push Messages).

3. Two-Way Confirmation (Accept / Decline Buttons)

  • Replace plain text reminders with LINE Template or Flex Messages.

  • Include Accept and Decline buttons using Postback actions.

  • Postback data must include Planning Center IDs (Person ID, Plan Person ID).

  • Build a second Make scenario to:

    • Listen for postback events.

    • Parse the action (accept / decline).

    • PATCH Planning Center via API to update the volunteer’s status.

    • Send an immediate LINE Reply Message confirming the action.

Technical Requirements

  • Make.com (Integromat): advanced scenario building

  • Planning Center API (Services + People)

  • LINE Messaging API (Push, Reply, Postback handling)

  • REST / HTTP methods (GET, POST, PATCH)

  • JSON payload construction and parsing

  • Webhook configuration and testing

What I Will Provide

  • Planning Center account access

  • LINE Official Account access

  • Make.com account

  • Clear architecture and logic (already designed)

  • Test users for validation

What I Expect From You

  • Clean, well-structured Make scenarios

  • Clear naming and basic documentation of scenarios

  • Secure handling of API keys

  • Ability to test and troubleshoot edge cases

  • Fast communication and ability to deliver independently

Timeline

  • Target completion: 1–2 weeks

  • Faster is welcome if quality is maintained

Budget

  • Open to a fixed-price project

  • Expected range: USD $300–$500, depending on experience and speed

  • Please propose a price and estimated hours

Ideal Candidate

  • Has built Make.com / Integromat automations using APIs

  • Has worked with messaging platforms (LINE, WhatsApp, Telegram, etc.)

  • Comfortable reading API documentation and implementing custom calls

  • Can work efficiently without heavy hand-holding

5 Likes
3

Hello @Todd_Blackhurst , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications

4

Hi @Todd_Blackhurst,

With over 5+ years of experience in automation, production-ready workflows are built using Make.com, REST APIs, and messaging platforms like LINE. Strong hands-on experience includes webhook-based identity linking, scheduled automations, and two-way messaging with postback actions integrated into Planning Center.

The focus is on clean, deterministic scenario design that ensures reliable user linking, consistent message delivery, accurate volunteer status updates, and easy maintenance in Make.com.

Happy to help build a stable and scalable solution for this integration. You can view the Fiverr profile or connect on LinkedIn. Also available for a quick call to discuss requirements.

5

I see you need a production-ready Make integration that links Planning Center with a LINE Official Account, including identity linking, scheduled reminders, and two-way accept/decline confirmations via the LINE Messaging API. The key is clean API handling, reliable webhooks, and well-structured Make scenarios so nothing breaks at scale.

I can implement this exactly as designed using advanced Make features, Planning Center APIs, and LINE push/reply/postback flows, with secure credentials, clear naming, and solid edge-case handling.

I can complete it within 5 - 7 days

If this sounds aligned, let’s do a quick chat here to confirm scope and timeline and get started.

7

Hello @Todd_Blackhurst ! I believe our automation expert could help you with this! Check your inbox, I’ve sent some more information in a private message :smiley:

8

Hi @Todd_Blackhurst ! I would love to help you with your scenario.

We are a small team of make.com experts and have developed plenty of complex integrations. This project should not be a challenge to us.

If you are interested we would love to help you, you can schedule a call in HERE discovery or check our website www.aspirity.com

9

This is a good fit for the type of API-driven Make.com integrations we build at Hashlogics. We work heavily with webhook-based identity linking, multi-service orchestration, and messaging APIs, so the Planning Center ↔ Make ↔ LINE flow maps closely to patterns we already use in production systems.

For context, our AI-Powered ESG Sustainability Platform shows how we structure long-running automations, external API calls, and secure data syncing in regulated environments:
:page_facing_up: ESG Case Study: https://drive.google.com/file/d/1Ace8kGEDlAXbScKwezalrV5aSESY4B9p/view?usp=sharing

We apply similar architecture in QA.Tax (https://www.qa.tax/), an IRS “Escape Plan” assistant that uses webhook triggers, structured JSON payloads, and multi-step API updates. Here’s a short walkthrough showing our approach to clean routing and payload handling:
:movie_camera: Loom: https://www.loom.com/share/e65b8f51ca0c426bac85751817cebb3c?sid=4e0e37d4-297f-45c4-81c4-6a45a51d37d9

Your three modules — one-time identity linking, weekly outbound reminders, and two-way accept/decline updates — are all straightforward with Make using HTTP modules, iterators, routers, and webhook listeners. The architecture you’ve outlined is clear, and we can implement it cleanly with proper documentation and naming so it’s easy to maintain long-term.

Let’s schedule a quick call so you can walk me through your exact payloads and event mapping, and I can outline how we’ll implement the scenarios end-to-end.
:date: Pick a slot here: https://calendly.com/_hashlogics/abdul-basit

Happy to get this built smoothly and production-ready.