Moss

In flight

The Moss connector ships with the Conversational FP&A recipe build. This page is a stub of the planned spec — file an issue if you need it sooner.

Connect to Moss to import card transactions, spend by merchant/category/employee, and budget tracking. Used by EU entities — pair with Ramp for US.

Setup

1. In Moss, request an API key via your account manager (Moss API access is allow-listed).
2. Configure a webhook endpoint for near-real-time updates.

Configuration

curl -X POST $API/api/v1/sources \
  -H "authorization: Bearer $TOKEN" -H 'content-type: application/json' \
  -d '{
    "name": "moss-de",
    "connector": "moss",
    "realm": "fin-master",
    "config": {
      "api_key": "…",
      "entity": "de",
      "webhook_secret": "…"
    }
  }'

Field	Type	Required	Description
api_key	secret	Yes	Moss API key.
entity	string	No	Free-form tag the recipe joins on. Use de to match the FP&A recipe.
webhook_secret	secret	No	For near-real-time webhook verification.

Tools (planned)

• moss.list_transactions(date_range, filters)
• moss.list_cards()
• moss.get_category_spend(category, period)

Spend normalization with Ramp

The FP&A agent uses a spend-model-normalization skill that joins Ramp + Moss transactions by:

• HiBob email as the canonical employee key
• Normalized merchant categories
• Date-of-transaction FX (Moss reports EUR; Ramp reports USD)

Used by

• Recipe: Conversational FP&A — combined with Ramp for US