Reference · built on requestOperator by FibricSales, quotes & revenue

Renewal Reminder

Flags subscriptions and contracts nearing term end and proposes the renewal notice with open tickets and usage attached.

Request accessPricing ↗

About

Renewal Reminder reads term ends from your billing system and your CRM. In Stripe that is a subscription item's current_period_end together with cancel_at_period_end. In Chargebee it is current_term_end and next_billing_at, with status non_renewing as a warning. In Recurly it is current_term_ends_at and auto_renew. In Salesforce it is a Contract's EndDate with OwnerExpirationNotice.

For each account inside your notice window it gathers open tickets from the service desk and metered usage from the billing meters, then proposes the renewal notice as a draft for the account owner with those attached. The owner reviews and sends. Accounts already set to cancel are flagged separately.

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

  • Stripe subscriptions with status, cancel_at_period_end, cancel_at, collection_method, and each subscription item's current_period_end
  • Chargebee subscriptions with status (active, non_renewing, paused), current_term_end, next_billing_at, remaining_billing_cycles, and contract_term
  • Recurly subscriptions with state, current_term_ends_at, auto_renew, and remaining_billing_cycles, filtered through GET /subscriptions by state
  • Salesforce Contracts with AccountId, StartDate, ContractTerm, EndDate, OwnerExpirationNotice, and StatusCode; HubSpot renewal deals by closedate and dealstage
  • Open tickets for the account: Zendesk tickets through the Search API, Intercom conversations searched by contact_ids with open true
  • Usage this term from Stripe meter event summaries (GET /v1/billing/meters/:id/event_summaries) or Chargebee usage records by subscription_id

Proposed actions

  • Target capability: propose the renewal notice as a mailbox draft for the account owner, with term end, open tickets, and usage in the body
  • Target capability: propose a renewal deal in the CRM: a HubSpot deal with closedate at term end, or a Salesforce Task on the Contract
  • Target capability: propose a separate flag for subscriptions with cancel_at_period_end true or status non_renewing, routed to the owner before the notice
  • Target capability: propose a Slack or Teams message to the account team listing accounts entering the window this week

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

What you can build

  • Stripe term end with Zendesk tickets

    Inside your window before current_period_end, pull the customer's open Zendesk tickets and meter summaries and draft the notice in the owner's Gmail.

    With Stripe, Zendesk, Gmail API

  • Chargebee non_renewing watch

    List subscriptions with status non_renewing or cancelled_at set and propose an owner task in HubSpot with the reason recorded in cancel_reason.

    With Chargebee, HubSpot

  • Salesforce Contract expiry

    Read Contracts whose EndDate falls inside the OwnerExpirationNotice period, attach Intercom conversations for the account contacts, and propose a Task on the Contract.

    With Salesforce Sales Cloud, Intercom

  • Recurly auto_renew off

    For subscriptions with auto_renew false and current_term_ends_at approaching, post the list to the account team in Slack with each owner named.

    With Recurly, Slack

Requirements

  • A billing system with term dates: Stripe, Chargebee, or Recurly
  • A CRM that names the account owner: Salesforce Contracts or HubSpot deals and companies with hubspot_owner_id
  • A service desk searchable by customer: Zendesk or Intercom
  • Your notice window and, for metered plans, the meter ids to summarise
Authentication
A billing API key with subscription and usage read access, a CRM token with contract or deal scopes, a service-desk token with search rights, and a mailbox draft scope for each owner.

Limits

  • It drafts the notice. It never changes a subscription, a price, or a term end.
  • Usage comes from meter event summaries, which Stripe describes as eventually consistent, so the figure in a draft can lag recent events.
  • A contract stored only as a PDF is invisible. Term ends must be fields in billing or the CRM.
  • An account with no owner in the CRM produces a proposal addressed to nobody and is listed for a manager to assign.

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 Renewal Reminder ↗

Questions and answers

What does the account owner approve?
A draft renewal notice with the term end, the open tickets, and this term's usage already in it. They edit and send, or hold it. For accounts set to cancel, the proposal is a flag to call first, and approving it records that choice.
Where do the usage figures come from?
From the billing system's own usage records: Stripe meter event summaries for the customer and meter, or Chargebee usage entries by subscription_id and item_price_id. It sums nothing on its own and never edits a usage record.
What record remains after a reminder?
Account and subscription ids, the term end read, the tickets and usage attached, the draft or flag proposed, who approved it, and when. The draft is the only artefact created and deleting it reverses the step.
Ask about Renewal Reminder

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