Bring no-code workflow results into one inbox

Start with a result you need to check or act on. Send a completion, an exception or a request for attention after your workflow knows the outcome.

• Title: say what happened, such as Catalog import needs review.
• Source: use the FYInbox source selected by the API key. A source label in JSON is descriptive and does not change that scope.
• Tags: use durable categories such as catalog and review.
• Metadata: keep non-secret references and counts as strings.
• Action: link to the report or source record where you will continue.

{
  "title": "Catalog import needs review",
  "body": "The example workflow accepted 148 records. Two records need attention.",
  "severity": "warning",
  "source": "example-catalog-workflow",
  "tags": [
    "catalog",
    "review"
  ],
  "deduplicationKey": "catalog:example-batch-1042:review",
  "metadata": {
    "batch": "example-batch-1042",
    "accepted": "148",
    "rejected": "2"
  },
  "actions": [
    {
      "id": "open-report",
      "type": "link",
      "label": "Open import report",
      "href": "https://example.com/imports/example-batch-1042",
      "style": "primary"
    }
  ]
}

In n8n, use an HTTP Request node. In Zapier, use a generic API request; API by Zapier currently requires a paid plan and is in beta. Configure POST to https://fyinbox.com/api/v1/notifications with a JSON body and source bearer authentication.

Save the key in the tool's credential connection. Keep it out of titles, metadata, links and shared workflow examples. The JSON above is an example payload, not an importable n8n workflow or Zap.

Use one stable deduplication key per logical outcome. A new notification returns 201 with created: true. A retry with the same key returns 200 with created: false and the original ID, while that notification exists.

Correct authentication and validation errors before retrying. Respect Retry-After on 429 responses. After a timeout or server error, retry a create request only with a stable deduplication key because the first request may already have succeeded.

Sign in to the same account on your phone or computer to review the stored inbox. Use source, tag, severity and exact metadata filters. Open the linked report to continue in the source system, then mark the notification read or archive it in FYInbox.

The active web inbox polls every ten seconds and refreshes when it regains focus. Web Push is optional and requires a subscription in each browser. An agent with the returned notification ID can retrieve that notification through its source-scoped API key; this does not mark it read.