Introduction to Automations & Integrations
Platform Automations react to events in GFoundry and act on them for you. Third-party automations connect GFoundry to other apps through Make.com and Zapier.
What are Platform Automations?
Platform Automations run actions automatically when something happens in GFoundry. You choose a trigger from a fixed catalog, such as a new user signing up, a user being added to a group or team, the user hire date, or a mandatory training milestone, and GFoundry does the rest:
Single-action automations add users to groups, remove them from groups, or assign a career when the event happens.
Multi-step automations run a pipeline of delays, emails, and push notifications, for example onboarding messages after the hire date or reminders before a training deadline.
You manage them in the backoffice under Automations, where you can also follow each run in Executions. See Platform Automations: overview and how to create one.
What are third-party automations?
Third-party automations connect GFoundry with other apps. GFoundry provides a GFoundry app for Make.com and for Zapier. Once it is installed and connected with an API key from your backoffice, you can build workflows in those tools with the other apps they support, such as Microsoft Teams, Slack, Google Sheets, or Salesforce. These connections run through Make.com or Zapier: GFoundry does not offer direct, built-in integrations with those apps.
Frequently asked questions
Are there pre-built integrations?
Yes. GFoundry offers a GFoundry app for Make.com and for Zapier. You install it from Automations in the backoffice, using the Set Up Make.com Automation or Set Up Zapier Automation button. See Third-Party Automations: Make.com and Zapier.
Can I create my own triggers?
No. Platform Automations use the trigger types in the catalog. You choose a trigger, then configure its groups, teams, or pipeline steps, recipients, and message content. For events outside the catalog, use the GFoundry app on Make.com or Zapier. See Automation trigger types and categories.
How do I troubleshoot an automation?
Open the automation and check that it is Enabled and that its groups, teams, and steps are set as you expect. Then review its Executions: each run shows its status, and for multi-step runs, View Details shows which step failed and why. If the problem continues, contact support.
Can I request a new integration or automation?
Yes. Send your suggestion to support. We review requests as we evolve the platform.

