Creating Program Integrations
Integrations allow you to connect Gloo Impact with your existing tools and systems, enhancing the functionality and automation of your programs.
Practical Use Cases for Integrations
Integrations can significantly streamline your workflow and enhance the experience for both your organization and your participants. Here are some practical use cases:
CRM Integration: Use webhooks to automatically add new applicants to your Customer Relationship Management (CRM) system when they join your waitlist or begin your program.
Learning Management System (LMS) Integration: When an applicant is approved for a program, use a webhook to trigger an automatic enrollment in your LMS. This seamlessly connects the Gloo Impact application process with your educational content delivery.
Milestone Verification Automation: Utilize API keys to automatically verify milestones based on data from your internal systems. For example, if a milestone requires attending a workshop, your attendance tracking system could automatically call the Gloo Impact API to verify completion once attendance is recorded.
Financial System Integration: When a payment is received, use a webhook to automatically update your accounting software, ensuring your financial records are always up-to-date without manual data entry.
Communication Automation: Set up webhooks to trigger personalized email or SMS notifications to stakeholders when milestone statuses change, keeping everyone informed in real-time.
Custom Application Processes: Implement API calls to create a fully customized application process on your website, while still leveraging Gloo Impact's backend for managing programs and funds.
These integrations can significantly reduce manual work, minimize data entry errors, and provide a more seamless experience for both your team and your participants. By leveraging webhooks and API keys, you can create a powerful, interconnected system that enhances the efficiency and effectiveness of your social impact initiatives.
Setting Up Webhooks
Navigate to the Integration Settings for your organization.
In the Webhook section, set up webhooks for:
Applicant Joined Waitlist
Applicant Ready for Program
Milestone Status Changed
Payment Received
For each webhook:
Click "Add Webhook" or a similar button.
Enter the webhook URL from your external system (e.g., Zapier, your CRM, or custom tool).
Save the webhook configuration.
Tip: Use webhook.site for testing before connecting to your actual systems.
Creating and Managing API Keys
In the Integration Settings, locate the API Key section.
Click "Create New API Key" or a similar option.
Name your API key based on its intended use.
Copy the generated key immediately – it won't be shown again.
Store the key securely (e.g., in a password manager or secure secret store).
Important: Never share your API key publicly. If compromised, revoke it immediately and create a new one.
Implementing External Service Verification
For milestones requiring external verification:
Configure the milestone to require external service verification in your program milestone setup.
Note the milestone_key for each milestone requiring verification.
In your external system:
Listen for the "Milestone Status Changed" webhook event.
When a milestone status changes to "pending verification", use the API to verify the milestone.
Testing Your Integrations
Use the unlisted program link to simulate an applicant joining the waitlist.
Check your webhook endpoint to confirm receipt of the "Applicant Joined Waitlist" event.
Simulate a participant going through your program:
Apply to the program
Complete milestones
Submit reflections and surveys
Verify that your external systems receive the appropriate webhook events.
Test your external service verification by responding to "pending verification" statuses.
Monitoring and Troubleshooting
Use the Webhook Logs in the Integration Settings to review event deliveries and identify issues.
For API-related issues, check your API key status and ensure correct endpoint and parameter usage.
Note: Always test your integrations thoroughly in the unlisted state before making your program public.