---

name: fondo-deploy-integration description: 'Deploy financial dashboards and reporting tools that consume Fondo data

to Vercel, Fly.io, or internal infrastructure.

Trigger: "fondo dashboard deploy", "fondo financial dashboard", "deploy finance app".

' allowed-tools: Read, Write, Edit, Bash(npm:*), Grep version: 1.6.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:

• saas
• accounting
• fondo compatibility: Designed for Claude Code

---

Fondo Deploy Integration

Overview

Deploy a containerized Fondo tax and accounting integration service with Docker. This skill covers building a production image that connects to Fondo's API for managing tax filings, compliance status, and financial reporting. Includes environment configuration for multi-entity accounting setups, health checks that verify API connectivity to Fondo's compliance endpoints, and rolling update strategies for zero-downtime deployments during critical tax filing periods.

Prerequisites

• A deployment owner, scoped runtime identity, approved data destinations, synthetic staging fixtures, and rollback operator.
• Health checks that expose generic status only and a policy prohibiting financial data/secrets in images and logs.

Instructions

1. Build reproducibly, inject secrets through the approved platform, and run the service with least privilege.
2. Validate schema, destination, and access controls using fictional data in staging before a canary.
3. Monitor aggregate health and reconciliation signals; stop and roll back on permission, data-boundary, or integrity failures.

Output

Record release/image ID, environment, approved configuration reference, canary result, owner, and rollback outcome. Exclude any financial, tax, payroll, account, or credential data.

Examples

Deploy a staging image with a fictitious export, simulate an upstream failure, and confirm health returns no sensitive payload. Roll back the canary before production if a destination or permission check fails.

Docker Configuration

FROM node:20-slim AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY tsconfig.json ./
COPY src/ ./src/
RUN npm run build

FROM node:20-slim
RUN addgroup --system app && adduser --system --ingroup app app
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY package*.json ./
USER app
EXPOSE 3000
HEALTHCHECK --interval=30s --timeout=5s --retries=3 \
  CMD curl -f http://localhost:3000/health || exit 1
CMD ["node", "dist/index.js"]

Environment Variables

export FONDO_API_KEY="fondo_live_xxxxxxxxxxxx"
export FONDO_BASE_URL="https://api.tryfondo.com/v1"
export FONDO_COMPANY_ID="comp_xxxxxxxxxxxx"
export FONDO_FILING_YEAR="2026"
export LOG_LEVEL="info"
export PORT="3000"
export NODE_ENV="production"

Health Check Endpoint

import express from 'express';

const app = express();

app.get('/health', async (req, res) => {
  try {
    const response = await fetch(`${process.env.FONDO_BASE_URL}/compliance/status`, {
      headers: { 'Authorization': `Bearer ${process.env.FONDO_API_KEY}` },
    });
    if (!response.ok) throw new Error(`Fondo API returned ${response.status}`);
    res.json({ status: 'healthy', service: 'fondo-integration', timestamp: new Date().toISOString() });
  } catch (error) {
    res.status(503).json({ status: 'unhealthy', error: (error as Error).message });
  }
});

Deployment Steps

Step 1: Build

docker build -t fondo-integration:latest .

Step 2: Run

docker run -d --name fondo-integration \
  -p 3000:3000 \
  -e FONDO_API_KEY -e FONDO_BASE_URL -e FONDO_COMPANY_ID -e FONDO_FILING_YEAR \
  fondo-integration:latest

Step 3: Verify

curl -s http://localhost:3000/health | jq .

Step 4: Rolling Update

docker build -t fondo-integration:v2 . && \
docker stop fondo-integration && \
docker rm fondo-integration && \
docker run -d --name fondo-integration -p 3000:3000 \
  -e FONDO_API_KEY -e FONDO_BASE_URL -e FONDO_COMPANY_ID -e FONDO_FILING_YEAR \
  fondo-integration:v2

Error Handling

Issue	Cause	Fix
401 Unauthorized	Invalid or expired API key	Regenerate key in Fondo dashboard settings
403 Forbidden	Company ID mismatch with API key	Verify FONDO_COMPANY_ID in Fondo account settings
404 Not Found	Filing or entity does not exist	Check filing year and entity IDs against Fondo portal
429 Rate Limited	Exceeding API rate limits	Implement exponential backoff; cache compliance status
Stale compliance data	Webhook not configured for updates	Register webhook endpoint in Fondo settings

Resources

• Fondo Platform

Next Steps

See fondo-webhooks-events.