Transactions

tags.notion.sync

Sync a linked project with Notion now, with tagId and idempotencyKey (linked projects also sync about hourly). Fields change only on the side that isn't the source of truth. A field the other side changed since they last agreed is not overwritten: it is returned in project.conflicts for a person to resolve with accounting_tags_notion_resolve.

POST/api/v1/accounting/tags.notion.sync

Permissions

accounting:readaccounting:write

Who can call it

admin, finance

Retries

Idempotency key required

MCP

accounting_tags_notion_sync

Reaches outside Oatmilk

It emails people or calls another service.

Fields

  • tagIdstring (ID)Required

    The ID of a project tag, from tags.list.

  • idempotencyKeystringRequired

    Any unique text you generate once per intended change, so a retried request only happens once. Send it as the Idempotency-Key header instead if you prefer; if you send both they must match.

    8–200 characters

Example

curl https://app.getoatmilk.com/api/v1/accounting/tags.notion.sync \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "tagId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10"
}'
Response
{
  "data": { … }
}

Try it

Try it

Checks your input with this action’s real schema and answers like the API, with synthetic data. No key needed, and nothing changes.

POST/api/v1/accounting/tags.notion.sync
curl https://app.getoatmilk.com/api/v1/accounting/tags.notion.sync \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "tagId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10"
}'

More in Transactions.