Reference · built on requestOperator by FibricReporting & analysis

Morning Brief

The day's operating brief drafted from overnight orders, contacts, and shipments, each number sourced, proposed for posting.

Request accessPricing ↗

About

Every morning someone opens four tabs and types the same numbers into a message. This operator does that assembly. Overnight is the window from the last brief to now. It reads orders placed, cancelled, or refunded in that window from your storefront, tickets opened and solved from your help desk, labels created and voided from your shipping tool, and the governed metric tables in your warehouse. Every figure in the draft carries the query or record list it came from.

The draft is proposed as a message to the channel you name. A person reads it, edits it, and approves the post. Items that need an owner become proposed follow-ups.

This is a reference listing. It documents what Fibric would read from Morning Brief and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Orders created, updated, or cancelled since the last brief, listed from the Shopify Orders resource by created_at and financial and fulfillment status
  • Tickets created and solved overnight through Zendesk incremental exports, keyed by start_time and read to end_of_stream
  • Shipments with labels created, and labels voided, from the ShipStation shipments list by createDateStart and voidDate
  • Governed daily metric rows in a warehouse table or view you name in Snowflake or PostgreSQL
  • Yesterday's posted brief and the follow-ups it created, so unfinished items carry forward
  • The channel it posts to and its thread, read back to see replies and corrections

Proposed actions

  • Target capability: propose the brief as a message to a named Slack channel, each number linked to the records behind it
  • Target capability: propose a follow-up item for each exception in the brief, addressed to the person you map to that queue
  • Target capability: propose a threaded correction when a source number changes after the brief is posted
  • Target capability: propose a saved copy of the brief and its figures to a warehouse table for the weekly review

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Post the brief to Slack from Shopify and Zendesk

    Overnight orders, cancellations, new tickets, and solved tickets are drafted into one Block Kit message. You approve it; it posts once to the channel and records the ts the post returned.

    With Shopify, Zendesk, Slack

  • Brief a Teams channel from Magento and Kustomer

    Orders from Magento and conversations from Kustomer are summarized and proposed as a channel message in Microsoft Teams, sent with the delegated permission of the person who approves it.

    With Magento, Kustomer, Microsoft Teams

  • Carry shipping exceptions forward

    Labels voided overnight in ShipStation become a follow-up list. Each item names the order and proposes an owner. Unresolved items reappear in the next brief until someone closes them.

    With ShipStation, PostgreSQL

  • Keep a table of every brief

    Each approved brief and its figures are proposed as one row per metric in a Snowflake table, so the weekly review reads the same numbers the team saw.

    With Snowflake, Slack

Requirements

  • A commerce connector with order timestamps and statuses: Shopify, Magento, or BigCommerce
  • A support connector that can list tickets by time: Zendesk, Kustomer, or Gorgias
  • A shipping connector with label create and void dates: ShipStation or EasyPost
  • A messaging connector and channel where the brief is posted: Slack, Microsoft Teams, or Google Chat
  • A posting time, a time zone, and the list of figures the brief carries, agreed before the first run
Authentication
A Slack app with chat:write for the channel, plus read access on the storefront, help desk, shipping, and warehouse connectors you attach.

Limits

  • Shopify returns orders older than 60 days only to apps granted read_all_orders. The brief reads the overnight window, so this affects backfills only.
  • Zendesk incremental exports return records changed at least one minute ago. A ticket solved seconds before the run lands in tomorrow's brief.
  • ShipStation lists only shipments whose labels it generated. Labels bought elsewhere and marked shipped by hand do not appear.
  • It posts to one channel per deployment. It does not send email or direct messages.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Morning Brief ↗

Questions and answers

What do I approve each morning?
One draft message. You see every figure, the query or record list behind it, and the follow-ups it proposes. Edit the text, drop a line, or approve. Nothing posts until you do, and it posts once.
What record does it leave?
The approved text, the figures with their sources, who approved it, the time it posted, and the message id the channel returned. Corrections are threaded under the original and recorded the same way.
What does it never do on its own?
It never posts, edits a posted message, sends a direct message, or opens a task without approval. If a source is unreachable at run time, the draft says which figures are missing rather than estimating them.
Ask about Morning Brief

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy