Use Paravant as a Zap step to create or find a client, update their details, link them to a trademark, or save a document. Each step works in the Paravant account connected to it. For connection steps, see Connecting Zapier to Your Account.
Choose the right step
Step | Fields | Result |
Create Client | Unique Identifier, plus any contact details, address, or Client Note | Creates a new client. An existing identifier returns |
Update Client | Unique Identifier, plus at least one profile field or non-empty Client Note | Changes selected details or appends a note. The client must already exist. |
Find Client | Exactly one of Unique Identifier, Contact Email, or Contact Phone | Finds one existing client. It does not create a client automatically. |
Link Client to Trademark | Client Unique Identifier and Serial Number | Links an existing client to a trademark already on your docket. Use the application serial number. |
Add Document to Client Record | Client Unique Identifier, File, and optional Document Name | Adds a file to an existing client's documents. |
Set up and test
Choose the step and connect the correct Paravant account.
Map the required fields from your earlier Zap steps.
Test with a recognizable test client. Create, update, link, and upload tests affect real records.
Inspect the client in Paravant and review the returned result before publishing your Zap.
Field values
Field | Values and requirements |
Unique Identifier / Client Unique Identifier | A permanent client ID, such as |
Client Name | Client name as text. |
Contact Email | Email address, such as |
Contact Phone | Phone number with country code, such as |
Address fields | Line 1, Line 2, City, State Province Region, Postal Code, and Country. Postal codes are text. |
Serial Number | Application serial number as text. The trademark must already be on your docket. |
Client Note | Text up to 5,000 characters. Adds a new note to the client record. |
File | A file from an earlier step or a direct HTTP/HTTPS download link accessible without your browser login. Non-empty; maximum 100 MB. Supported types include PDF, Word, spreadsheets, presentations, text, and common images. |
Document Name | Optional filename, including the correct extension. |
Find a client
Search using exactly one of Unique Identifier, Contact Email, or Contact Phone.
Search result | What happens |
One match | Returns the client. Use its Unique Identifier in later actions. If missing, assign one to that client in Paravant first. |
No match | Returns no results. Your Zap can stop or follow a separate create path. |
Multiple matches | Returns |
Update a client
Input | Effect |
Profile field omitted | Existing value stays unchanged. |
Profile field explicitly sent empty or | Clears that optional value. |
Client Note supplied | Appends a note; preserves earlier notes. |
Only a note changes | Result can be |
Check the sent data in Zap history when testing: an empty-looking input may be omitted or sent empty. Replaying a successful note or document step can add another copy. Create Client identifies duplicates by Unique Identifier, not name or email.
For document uploads, use the downloadable file rather than a sharing or preview page, and open the uploaded document during testing.
Resolve common problems
Client or case not found: Check the connected account, exact identifier, and serial number. Both records must exist before linking.
Clio-managed field or relationship: Make the change in Clio.
File download failed: Refresh an expired link and map the actual file output.
Uncertain result: Inspect Paravant before retrying. If the problem persists, contact Paravant support with the failed step and error message.
