brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
fondo-webhooks-eventsImplement event-driven financial workflows using webhooks from Fondo-connected services: Stripe payment events, Gusto payroll events, and Plaid transactions. Trigger: "fondo webhooks", "fondo events", "stripe payroll webhooks", "financial events".
Independent GitHub snapshot · Automated classification · Original documentation governs
name: fondo-webhooks-events description: 'Implement event-driven financial workflows using webhooks from Fondo-connected
services: Stripe payment events, Gusto payroll events, and Plaid transactions.
Trigger: "fondo webhooks", "fondo events", "stripe payroll webhooks", "financial events".
' allowed-tools: Read, Write, Edit, Bash(npm:*) version: 1.6.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:
A signing secret in the secret manager, raw-body validation, event ledger, approved destinations, redaction policy, and synthetic fixtures.
Return opaque event ID, signature result, idempotency outcome, destination status, and redacted error category. Keep financial payloads and credentials out of logs.
Reject invalid signatures, quarantine unknown schemas or destinations, bound retries, and pause downstream processing on access or reconciliation failures.
Deliver a fictional signed event twice and confirm only the first is processed; reject an invalid signature without logging its payload or forwarding data.
Fondo itself does not send webhooks. Instead, build event-driven workflows using webhooks from the same providers Fondo connects to: Stripe (revenue), Gusto (payroll), Plaid (bank transactions), and Mercury (banking).
| Provider | Key Events | Use Case |
|---|---|---|
| Stripe | charge.succeeded, invoice.paid | Revenue tracking, MRR alerts |
| Gusto | payroll.processed, employee.created | Payroll cost alerts, headcount |
| Plaid | transactions.sync, item.error | Expense monitoring |
| Mercury | transaction.created | Real-time spend tracking |
import Stripe from 'stripe';
const stripe = new Stripe(process.env.STRIPE_API_KEY!);
app.post('/webhooks/stripe', express.raw({ type: '*/*' }), (req, res) => {
const sig = req.headers['stripe-signature'] as string;
const event = stripe.webhooks.constructEvent(
req.body, sig, process.env.STRIPE_WEBHOOK_SECRET!
);
switch (event.type) {
case 'charge.succeeded':
const amount = (event.data.object as Stripe.Charge).amount / 100;
console.log(`Revenue: ${amount}`);
// Update internal dashboard
break;
case 'invoice.paid':
// MRR tracking
break;
}
res.sendStatus(200);
});
// Gusto sends webhooks when payroll is processed
app.post('/webhooks/gusto', express.json(), async (req, res) => {
const { event_type, data } = req.body;
if (event_type === 'payroll.processed') {
const totalPayroll = data.totals.gross_pay;
console.log(`Payroll processed: ${totalPayroll}`);
// Alert if significantly different from budget
if (totalPayroll > monthlyPayrollBudget * 1.1) {
await sendAlert(`Payroll exceeded budget by ${((totalPayroll / monthlyPayrollBudget - 1) * 100).toFixed(0)}%`);
}
}
res.sendStatus(200);
});
For performance optimization, see fondo-performance-tuning.