Reference · built on requestOperator by FibricSales, quotes & revenue

Sample Request

Turns each sample request into a proposed shipment, checks sample stock and prior requests, and sets the follow-up date.

Request accessPricing ↗

About

Sample Request reads each request as it lands: a HubSpot deal entering your sample stage, a Pipedrive lead or deal flagged for samples, or a contact whose form answers name the sample SKUs. It checks sample stock in Katana by variant and location, or in Zoho Inventory by sku and stock on hand, and it looks for earlier shipments to the same contact or company.

It then proposes the shipment: a ShipStation order with the sample items and the ship-to address, or a Shippo shipment with rates to pick from, plus a follow-up task on the deal dated from the expected delivery. A rep approves. Nothing ships until they do.

This is a reference listing. It documents what Fibric would read from Sample Request 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

  • Requests in the CRM: HubSpot deals whose dealstage is your sample stage, with associated contact, company, and line items carrying hs_sku and quantity
  • Pipedrive leads and deals with owner_id and expected_close_date, and the activities already logged against them
  • Sample stock in Katana: inventory rows with variant_id, location_id, quantity_in_stock, quantity_committed, and quantity_expected
  • Sample stock in Zoho Inventory: items with sku, stock_on_hand, available_stock, and reorder_level
  • Prior sample shipments: ShipStation orders keyed by orderKey with customerEmail and shipTo, and Katana sales orders by customer_id and status
  • Shippo shipment records with address_to and parcels, and the rates returned for each

Proposed actions

  • Target capability: propose a ShipStation order through POST /orders/createorder with orderStatus awaiting_shipment, the sample items by sku, quantity, and unitPrice, and internalNotes naming the deal
  • Target capability: propose a Shippo shipment with address_from, address_to, parcels, and the rate to buy, confirmed by a person before the label is purchased
  • Target capability: propose a follow-up task on the deal: a HubSpot task with hs_task_type CALL and hs_timestamp, or a Pipedrive activity with due_date
  • Target capability: propose a decline when the contact already received the sample, or a substitute when stock is short, for the rep to override
  • Target capability: propose holding the ShipStation order through POST /orders/holduntil when the rep wants it to leave on a chosen date

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

What you can build

  • HubSpot sample stage to ShipStation

    When a deal enters the sample stage, read its line items, check Katana quantity_in_stock for each variant, and propose the ShipStation order plus a CALL task after delivery.

    With HubSpot, Katana Cloud Inventory, ShipStation

  • Pipedrive request with Zoho stock

    Read the lead's sample SKUs, confirm available_stock in Zoho Inventory, and propose a Shippo shipment with the lowest rate and a due_date activity for the owner.

    With Pipedrive, Zoho Inventory, Shippo

  • Repeat request caught

    Search ShipStation orders by the contact's customerEmail and propose a decline, with the earlier order linked, when the same sku already went out.

    With ShipStation, HubSpot

  • Ship on a chosen date

    Propose the order held through POST /orders/holduntil with holdUntilDate so the sample lands the week of the customer's trial.

    With ShipStation

Requirements

  • A CRM stage or field that marks a request as a sample: HubSpot or Pipedrive
  • Sample SKUs held as stock in Katana or Zoho Inventory, with a location for samples if you keep one
  • A shipping tool that accepts orders by API: ShipStation or Shippo
  • A rep or sample desk who approves each shipment and owns the follow-up
Authentication
A CRM token with deal and task scopes, an inventory API key with stock read, and a ShipStation API key or Shippo token with order and shipment write rights.

Limits

  • It never buys a label or ships. A Shippo rate is proposed; the transaction runs only after approval.
  • Stock is read at proposal time. It does not reserve units, so two requests for the last sample are both shown short.
  • Duplicate detection matches on the contact's email and company. A request under a new email from the same person can pass.
  • The follow-up date is set from the delivery your shipping tool reports, or from a fixed offset you choose when none is available.

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 Sample Request ↗

Questions and answers

What does the rep sign off on?
The shipment: items, quantities, ship-to address, and the carrier rate, with stock levels and any earlier shipment to the same contact shown beside it. They approve, change the items or date, or decline. The follow-up task is created with the approval.
What happens when a sample is out of stock?
The proposal marks the line short, shows quantity_expected or the reorder level from your inventory system, and offers a substitute only if you have mapped one. It never creates a purchase order.
What record is left?
Request id, deal and contact, stock read per sku, prior shipments found, the order or shipment proposed, the follow-up date, who approved it, and when. A created ShipStation order can be cancelled from the entry while it is still awaiting shipment.
Ask about Sample Request

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