Communication
Email notifications
Approval requests, reminders and scheduled reports delivered by email.
Where this actually stands
PlannedPlanned
Designed and on the roadmap: we know what it would do and roughly what it takes. No code has been written, and we are not going to imply otherwise.
Connection type
Webhook
The other system tells G1 when something happens, so work starts on the event rather than on a timer.
What it would do
Email notifications, connected.
The fallback that always works.
G1 does not ask you to replace a system that works. Where a connection exists, the point of it is to remove the person in the middle — the weekly export, the re-key, the spreadsheet that reconciles two tools that should have agreed in the first place.
An approval that needs a new tab gets delayed. Notifications and approvals delivered into existing channels get actioned.
Every categoryModules it feeds
- WorkflowIn developmentApprovals and routing across the business, not just finance.
- ReportingAvailableStatements that tie back, every time, without a reconciliation ritual.
- Controls & approvalsAvailableApprovals, period locks and an audit trail that cannot be edited.
A connector is only as useful as the module reading it. Where the module is still in development, the connector waits for it.
Communication
Others in the same category.
- PlannedExplore
Webhook
Slack
Approvals and alerts in the channel people watch.
- PlannedExplore
Webhook
Microsoft Teams
The same approvals, in Teams.
- PlannedExplore
Webhook
WhatsApp Business
For teams that genuinely run on it.
Names listed here are trademarks of their respective owners and appear only to describe compatibility and connection plans. No partnership, endorsement or affiliation is implied, and no third-party logos are used anywhere on this site.
Connect what you already use
Tell us how Email notifications is used where you are.
What matters is not the connector — it is the work it removes. Describe the manual step and we will tell you whether a connection actually fixes it.