Integrations#

Self Hosted Cloud Hosted

BrewGraph supports imports, forwarding, and exports. In the Cloud Hosted beta, Brewfather and BeerXML batch imports and account exports are available. Forwarding and Brewfather write-back are coming soon on Cloud Hosted.

  • Importing — pulling batch/recipe data from an external source into BrewGraph

  • Forwarding — relaying every accepted reading out to another service, live

  • Export — sending data from BrewGraph back out on request

For a full local export or backup of an entire Self Hosted instance (not scoped to one integration), see Backup & Restore.

Importing#

Brewfather#

BrewGraph can pull a batch’s recipe metadata from Brewfather — see Batches for how credentials are handled on each edition. It’s a one-time pull with no ongoing sync: name, style, brewer, brew date, starting/final gravity, alcohol, bitterness, and colour targets, carbonation volumes, batch volume, notes, and fermentation-step details can come across, but those steps are not available in the Cloud Hosted beta. Brewfather does not provide conditioning_days; enter conditioning time in BrewGraph if needed. Batches in Brewfather’s “Planning” or “Brewing” status are the expected import candidates.

BeerXML#

BrewGraph can also pre-populate the batch creation form from a BeerXML file. The file is parsed entirely client-side — nothing is uploaded to BrewGraph’s servers. The file can fill in the name, style, starting/final gravity targets, bitterness, colour, batch volume, and notes. Fermentation-step data may be present in the file but steps are coming soon to Cloud Hosted. Open the web app in a browser to import; the mobile batch-creation flow does not offer it.

Forwarding#

Measurement forwarding#

On Self Hosted, BrewGraph can forward accepted gravity, pressure, pour, and temperature readings to another service. This is coming soon to Cloud Hosted. Forwarding is configured once, for the account as a whole — set up a target and every device (or, for pour, every tap) on the account forwards to it, rather than configuring a URL on each device individually.

Gravity readings can go to any of three target types:

  • iSpindel forward — relay readings in the iSpindel wire format to any compatible receiver.

  • Brewfather forward — relay readings to Brewfather’s stream endpoint, so Brewfather shows live fermentation data alongside a batch imported from it.

  • Custom — forward readings to any other service (Thingspeak, a home-grown webhook, and so on) by supplying a URL, an HTTP method, optional headers, and a template. The template supports placeholder tokens such as ${gravity}, ${temperature}, ${battery}, and ${deviceName}, which are filled in with each reading’s actual values as it forwards.

Pressure, pour, and temperature readings can only go to a Custom target — there’s no built-in Brewfather- or iSpindel-shaped equivalent for those measurement types.

Before saving a target, a Preview payload button shows exactly what will be sent — method, headers, and body — rendered against sample data. This preview runs entirely in your browser; nothing is sent anywhere until you save and a real reading arrives.

Self Hosted: Other → Integrations. Cloud Hosted forwarding is coming soon.

Export#

Brewfather write-back#

Cloud Hosted

Brewfather write-back is coming soon to Cloud Hosted. When available, it will send a packaged batch’s measured original and final gravity back to the Brewfather batch it came from. This is a deliberate, user-initiated action rather than an automatic sync.

Account data export#

Cloud Hosted

Every Cloud Hosted beta account can download its brewing data and a full backup from Settings > Data & Privacy, without closing the account.