Optimator
Let's Talk
← Our applications
Fireberry add-onMake appAction API

PulseBerry

Keep Fireberry screens in sync with the automations working behind them. Refresh an active record or display a live notification immediately after Make or another external system completes an action.

Install PulseBerry Quick start
LIVE ACTION
MakeScenario
APISecure trigger
FireberryActive record
recordId + objectType Refresh delivered
01Record refresh

Update the screen already open for the user.

02Live toast

Show contextual success, warning, error, or info messages.

03Make + API

Trigger actions from a scenario or any authenticated client.

Overview

External automation, visible immediately in Fireberry.

PulseBerry is a Fireberry side-menu application and an authenticated Action API. It watches the record currently open in each active Fireberry tab and delivers the right action only to matching sessions.

Targeted refresh

Refresh only tabs displaying the specified record and object type.

Contextual notifications

Display a toast on matching records or target a specific Fireberry user.

Realtime delivery

Authenticated SSE is primary, with automatic polling fallback.

Organization isolation

Tokens, users, sessions, activity, and quotas are scoped per organization.

Fireberry installation

Install the listener inside Fireberry.

  1. 1
    Request installation access

    Contact Optimator to receive the current Fireberry package or installation link.

  2. 2
    Open PulseBerry from the side menu

    On first use, choose English or Hebrew. The selection is saved per user.

  3. 3
    Allow account setup to complete

    The app identifies the Fireberry organization and provisions its isolated PulseBerry account.

  4. 4
    Copy the API token

    Open Settings in PulseBerry and copy the organization token beginning with fbr_.

  5. 5
    Keep Fireberry open

    Actions are delivered to active component sessions. Closed tabs expire automatically.

Installation access

The public Marketplace URL is not published yet. Request the current package from support@optimator.co.il.

Make app

Trigger PulseBerry directly from a Make scenario.

  1. 1
    Install the PulseBerry Make app

    Open the official invitation and add PulseBerry to your Make organization.

  2. 2
    Add a PulseBerry action

    Place the app after the module that updates Fireberry or completes the external process.

  3. 3
    Create a connection

    Paste the fbr_ organization token copied from the Fireberry side-menu settings.

  4. 4
    Map the target

    For record actions, map the Fireberry recordId and numeric objectType.

  5. 5
    Select the action

    Choose refresh, or toast and map its message, type, placement, close button, and timeout.

  6. 6
    Run once, then activate

    Open the target record in Fireberry, test the scenario, and verify the action before scheduling it.

Install PulseBerry for Make

Quick start

Send your first action.

Use the organization token as a Bearer token. Never expose it in a public browser application.

Refresh an active record
curl -H "Authorization: Bearer fbr_ACCOUNT_TOKEN" \
  "https://api.fbrefresh.com/actions/trigger?recordId=RECORD_ID&objectType=5&action=refresh"
Display a Fireberry toast
curl -G -H "Authorization: Bearer fbr_ACCOUNT_TOKEN" \
  --data-urlencode "recordId=RECORD_ID" \
  --data-urlencode "objectType=5" \
  --data-urlencode "action=toast" \
  --data-urlencode "content=The record was updated" \
  --data-urlencode "toastType=success" \
  --data-urlencode "placement=top-end" \
  --data-urlencode "withCloseButton=true" \
  --data-urlencode "autoDismissTimeout=5000" \
  "https://api.fbrefresh.com/actions/trigger"

API reference

Action endpoint

GEThttps://api.fbrefresh.com/actions/trigger

Authentication

Send Authorization: Bearer YOUR_ACCOUNT_TOKEN with every request.

ParameterRequiredDescription
recordIdRecord actionsThe Fireberry record identifier. Do not combine it with userId.
objectTypeRecord actionsThe numeric Fireberry object type.
actionNorefresh or toast. Defaults to refresh.
userIdUser toastTargets a Fireberry user on any page. Cannot include record targeting.
contentToastThe notification message.
toastTypeNosuccess, warning, error, or info.
placementNoToast placement, for example top-end.
withCloseButtonNoBoolean controlling the close button.
autoDismissTimeoutNoAutomatic dismissal timeout in milliseconds.

Response and quota headers

  • X-MonthlyQuota-Limit — monthly action limit.
  • X-MonthlyQuota-Remaining — actions remaining.
  • X-MonthlyQuota-Reset — next UTC reset.
  • RateLimit and Retry-After — per-minute throttling information.

An exceeded rate limit returns HTTP 429 with code RATE_LIMIT_EXCEEDED.

Related endpoints

  • GET/accounts/me

    Current account, plan, limits, and usage.

  • POST/accounts/token/rotate

    Invalidate the current token and return its replacement.

  • GET/actions/latest

    Authenticated side-menu action lookup.

  • POST/sessions/heartbeat

    Renew an active side-menu session during polling fallback.

Legacy /refresh/trigger and /refresh/latest routes remain available as aliases.

User-targeted toast
GET https://api.fbrefresh.com/actions/trigger?action=toast&userId=USER_ID&content=Hello&toastType=info&placement=top-end
Authorization: Bearer YOUR_ACCOUNT_TOKEN

Security & limits

One isolated account per Fireberry organization.

  • A cryptographically random fbr_ token is generated per organization.
  • Only its SHA-256 hash is stored by the API; the raw token stays in organization-scoped Fireberry app settings.
  • Free accounts receive 30 actions per UTC month. Other plans use configurable action, record, session, and request limits.
  • Commands have a 10-minute delivery lifetime. The target tab or user must have Fireberry open during that window.
  • Rotate a compromised token immediately. Rotation invalidates the previous token.
Treat the token like a password.

Store it only in Make connections or secure server-side secrets. Do not place it in frontend code, screenshots, or public documentation.

Troubleshooting

Common checks before contacting support.

The record did not refresh

Confirm the exact recordId and numeric objectType, keep the target record open, and verify PulseBerry is active in that organization.

The API returns 401

The token is missing, invalid, or was rotated. Copy the current token from PulseBerry Settings and reconnect the Make connection.

The API returns 429

The per-minute or monthly quota was exceeded. Read the quota and Retry-After response headers before retrying.

A user-targeted toast was not delivered

The user must have Fireberry open during the 10-minute command lifetime. Confirm that the supplied Fireberry user ID is correct.

Get access

Ready to connect PulseBerry?

Request the current Fireberry package or install the Make app directly. By installing or using PulseBerry, you agree to the Terms of Use and acknowledge the Privacy Policy.

Request Fireberry accessInstall for Make