Transactions

tags.notion.resolve

Resolve a sync conflict on one field (name, dates, status, budget or description) with tagId, field, keep (notion writes Notion's value to Oatmilk; oatmilk writes Oatmilk's value to Notion) and idempotencyKey. Then syncs the project.

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

Permissions

accounting:readaccounting:write

Who can call it

admin, finance

Retries

Idempotency key required

MCP

accounting_tags_notion_resolve

Reaches outside Oatmilk

It emails people or calls another service.

Fields

  • tagIdstring (ID)Required

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

  • fieldenumRequired
    namedatesstatusbudgetdescription
  • keepenumRequired
    oatmilknotion
  • 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.resolve \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "tagId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "field": "name",
  "keep": "oatmilk"
}'
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.resolve
curl https://app.getoatmilk.com/api/v1/accounting/tags.notion.resolve \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "tagId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "field": "name",
  "keep": "oatmilk"
}'

More in Transactions.