NEXT Impact 360Integrations
NEXT Impact 360 connects selected third-party services to the organization workspace. Availability depends on configuration, permissions, provider approval, and the customer’s plan.
Effective and last updated: July 14, 2026How integrations work
Integrations are activated by an authorized user or administrator. NEXT Impact 360 requests access needed for the enabled feature and uses connected data to provide that feature, maintain synchronization, protect the service, and troubleshoot failures. Connecting an integration does not transfer ownership of customer content.
Google Workspace
Purpose: Connects authorized Gmail mailboxes for correspondence and Google Calendar for tour scheduling and synchronization.
Data involved: Depending on the permissions a user grants: account identity, email messages and metadata, attachments, calendar events, and synchronization cursors.
Your control: A user can revoke Google access from the connected Google account. Administrators can disconnect the account in NEXT Impact 360.
Microsoft 365
Purpose: Connects authorized Outlook and Microsoft Graph accounts for email correspondence, drafts, subscriptions, and calendar workflows.
Data involved: Depending on granted permissions: account identity, email messages and metadata, attachments, calendar events, and subscription identifiers.
Your control: Access can be revoked in Microsoft account or tenant settings and disconnected from NEXT Impact 360.
Twilio Messaging
Purpose: Supports company-specific two-way SMS/MMS, delivery receipts, inbound replies, and standard consent keywords such as STOP, START, and HELP.
Data involved: Phone numbers, message content, media metadata, provider identifiers, delivery status, consent, and suppression records.
Your control: Organizations must obtain required consent and honor opt-outs. Recipients can use supported opt-out keywords.
Twilio SendGrid
Purpose: Delivers authorized email campaigns and processes delivery, bounce, complaint, and unsubscribe events.
Data involved: Recipient email addresses, message content, internal correlation identifiers, delivery events, and unsubscribe-group status.
Your control: Organizations control campaigns and recipient lists. Unsubscribe and suppression controls are applied before eligible sends.
Blackbaud Raiser’s Edge NXT
Purpose: Supports controlled constituent and action-note workflows through import/export files and configured note coordination.
Data involved: Only the constituent, note, identifier, and audit fields selected for the configured workflow.
Your control: Authorized staff review export queues and decide when records are exported, imported, archived, or resent.
OpenAI (optional)
Purpose: May support administrator-enabled drafting, summaries, or donor briefs. AI output is assistive and requires human review.
Data involved: Only information submitted by an authorized feature for the requested result. Availability depends on organization configuration.
Your control: Organizations can leave AI features unconfigured or disable their use. Users remain responsible for reviewing output.
Supabase and Vercel
Purpose: Provide core authentication, database, storage, server processing, and application hosting infrastructure.
Data involved: Account, session, application, audit, configuration, and customer-content data needed to operate and secure the service.
Your control: Access is limited through application roles, company boundaries, service credentials, and provider security controls.
Important provider terms
Third-party services are operated independently and remain subject to their own terms, privacy policies, availability, pricing, security practices, and technical limits. NEXT Impact 360 does not control or guarantee a provider’s service and is not responsible for provider outages, account restrictions, policy changes, delivery decisions, or data handling outside NEXT Impact 360’s control.
Google Workspace information is used in accordance with the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not sold, used for advertising, or used to train generalized artificial-intelligence models.
Customer responsibilities
Customers are responsible for configuring integrations correctly, protecting provider credentials, assigning appropriate permissions, obtaining required communication consent, honoring opt-outs, reviewing AI-assisted content, and complying with laws and provider policies that apply to their use.