Paravant triggers fall into two categories: upon event and date based. Use the payload sent to your Zap to create tasks, send messages, or update records in another app.
For setup, see Connecting Zapier to Your Account.
Upon event
An upon-event trigger runs when Paravant detects a matching trademark event—for example, Examiner Assigned. Its Paravant automation displays Upon Event and needs no reminder frequency.
Delivery follows Paravant's processing of the case update. An “instant” Zapier trigger means data is pushed to Zapier; it does not promise immediate detection of a USPTO change. Enabling a trigger does not export the case's full event history.
Date based
A date-based trigger runs on the reminder dates you select in Paravant, as a one-time reminder or recurring sequence. Choose the frequency in Automations → Configuration → Edit Automation Cadence and Content, not in Zapier.
Reminders require a matching automated deadline that is still pending. Enabling a schedule does not replay past reminder dates. Reminder-day boundaries use Eastern Time.
Payload
The payload is the information Paravant sends to your Zap. The tables below show exact field names and possible values. Quoted examples are text; null means no value, and [] means an empty list. Example values are illustrative, not live case data.
Field | Values and format |
Mark Identification | Trademark text, such as |
Serial Number | Text containing the application number, such as |
Registration Number | Text containing the registration number, such as |
Filing Date | Eastern calendar date as |
Registration Date | Eastern calendar date as |
Attorney Name | Recorded attorney name as text, such as |
Domestic Representative | Recorded representative as text; |
USPTO Docket Number | Attorney docket number as text; |
Office Action Link | Associated document URL as text, or |
Notification Sequence Count | The notification number for the deadline: |
Paravant Clients | A list of linked client objects: |
Date fields use YYYY-MM-DD.
Date-based deadline fields
These fields are absent from upon-event payloads. They are added to date-based payloads when the triggering deadline can be found; otherwise they will be absent.
Field | Values and format |
Due Date | The current deadline as |
Absolute Final Due Date | The potential last due date, factoring in available extensions or grace periods, as |
Absolute Final Due Date Reason |
|
Linked client fields
These fields belong to each object in Paravant Clients. Zapier displays them as line items, with labels such as Client - Contact Email.
Payload field | Values and format |
Client Name | Saved client name as text, such as |
Unique Identifier | Saved client identifier as text, such as |
Contact Email | Saved email as text, such as |
Contact Phone | Saved phone as text, such as |
Address | An object containing the six fields below; |
Address → Line 1 | Street-address text, such as |
Address → Line 2 | Additional address text, such as |
Address → City | City text, such as |
Address → State Province Region | Saved region text, such as |
Address → Postal Code | Text, such as |
Address → Country | Saved country text, such as |
portal_link | Client - Portal Link in Zapier. The client's portal URL. |
portal_cta_text | Client - Portal CTA Text in Zapier. Exact format: |
portal_cta_html | Client - Portal CTA HTML in Zapier. HTML paragraph containing a link with text |
