Integrations
7
Email, calendar, payments, website, prayer times, signage, and aid.
Ready
2
Low-risk integrations can be connected after credential setup.
Restricted
2
Payments, aid, and sensitive workflows need extra controls.
Rule
Approve
Outbound send, schedule, publish, and payment actions require review.
Integration Registry
Each connection is defined by purpose, data handled, ownership, direction, and next step.
| Integration | Category | Status | Direction | Visibility | Owner | Next Step |
|---|---|---|---|---|---|---|
Shared email inboxes Let the AI monitor masjid inboxes and summarize what needs a team response. Incoming questionsUnread response queuesStaff assignmentsFollow-up reminders | communication | ready_to_connect | inbound | staff | Operations Admin | Choose Gmail or Microsoft 365 mailbox strategy and define approved monitored inboxes. |
Internal masjid calendar Power religious leader appointments, Shura schedules, facility reservations, and vendor scheduling. AppointmentsRoom bookingsStaff availabilityPrayer leadershipVendor windows | calendar | planned | two_way | staff | Platform Admin | Build internal event model before connecting external calendar providers. |
Payments and reimbursements Track money movement across registrations, membership, supplies, donations, and expenses. DonationsRegistration paymentsMembership duesReimbursementsReceipts | payments | needs_credentials | two_way | restricted | Finance Lead | Decide Stripe, PayPal, Zelle manual tracking, and bank reconciliation approach. |
Masjid websites and CMS Keep AI knowledge current with public website content that changes weekly. PagesMenusSubmenusSlider contentPublic linksDonation pages | website | ready_to_connect | inbound | public | Content Admin | Create sitemap crawler and human review queue for changed pages and flyers. |
Prayer time source Normalize date-sensitive prayer data for signage and assistant answers. AdhanIqamahJummahEidRamadanCountdown windows | prayer_times | planned | inbound | public | Imam Office | Convert monthly PDFs or screenshots into structured schedule tables. |
TV signage players Publish approved announcements and prayer schedules to landscape and portrait TVs. SlidesUrgent alertsPrayer screensCountdown statesScreen orientation | signage | planned | outbound | public | Operations Admin | Define screen device registration and playlist publishing model. |
Amanah DFW portal Eventually integrate financial aid intake and casework while preserving privacy-first boundaries. Applicant profilesCase statusDocumentsCommittee votesDisbursements | casework | deferred | two_way | highly_restricted | Casework Lead | Keep as holding block until core platform modules are stable. |
Connection Principles
- Connect public data first, then staff data, then restricted data after roles and audit trails are enforced.
- Every integration must declare data direction, owner, visibility, credential owner, and failure behavior.
- AI can read from approved integrations but cannot send, pay, publish, or schedule externally without approval rules.
- Weekly-changing website flyers and slider images should enter a review queue before becoming trusted answers.
- Payment and financial aid integrations require stricter audit logs, retention, and export controls.