Foxit eSign + Webhooks by Zapier Integrations

How to connect Foxit eSign + Webhooks by Zapier

Zapier lets you send info between Foxit eSign and Webhooks by Zapier automatically—no code required.

When this happens...

automatically do this!

Free 14-day trial

5,000+ supported apps

Top companies trust Zapier to automate work and free up time

Connect your apps and automate workflows

Easy automation for busy people. Zapier moves info between your web apps automatically, so you can focus on your most important work.

By signing up, you agree to Zapier's terms of service and privacy policy.

Supported triggers and actions

What does this mean?

Document Cancelled
Triggers when a Party has declined to sign or cancels a Document. Required reason for cancelling and Party who cancelled included in this trigger. Available for our Paid or Trial Business Premium accounts.
Trigger
Instant
Try It
Document Executed
Triggers when ALL PARTIES have signed the Document. Triggers for a Single Party Document as well. Available for our Paid or Trial Business Premium accounts.
Trigger
Instant
Try It
Document Signed
Triggers when a Party has signed a Document. In case of a multiparty Documents: You get a separate trigger when each Party Signs the Document. Available for our Paid or Trial Business Premium accounts.
Trigger
Instant
Try It
- TemplateRequired
- Folder Name
- First NameRequired
- Last NameRequired
- EmailRequired
- PermissionRequired
- SequenceRequired
  Use this field to assign a sequence number to a recipient in the list of recipient parties. Use unique sequence numbers for each party starting with 1 like 1,2,3,4
- In Person Administrator Email
- Allow Signer to Correct Name
- Sender Email
- Enable Signing Sequence
  Use this field to send the folder signinig in sequence or not. When false, signing emails sent to all. When true, signing email are sent to next only after prior party signs.
- Send Now
- Enable In Person Signing
  When you are passing as a true then, Use this field to initiate the in-person signing process which can be easily completed on any device in a matter of minutes and avoids email-based signatures where required.
- Static Recipients
  Use this fieeld to freeze the recipient parties after creating a folder from the API in embedded mode. Parties are allowed to be edited only when value is false.
- Static Documents
  Use this fieeld to freeze the documents in a folder after creating a folder from the API in embedded mode. Documents are allowed to be edited only when value is false.
- Send Success URL
  URL for the landing page on your website/application, which the user will be redirected to after successfully sending the folder in the embedded sending view.
- Send Error URL
  URL for the landing page on your website/application, which the user will be redirected to if error comes during sending the folder in the embedded sending view.
- Sign Success URL
  URL for the landing page on your website/application, which the user will be redirected to after successfully signing the folder in the embedded signing view.
- Sign Decline URL
  URL for the landing page on your website/application, which the user will be redirected to if he declines to sign the folder in the embedded signing view.
- Sign Later URL
  URL for the landing page your website/application, which the user will be redirected to if he chooses to sign the folder later in the embedded signing view.
- Sign Error URL
  URL for the landing page your website/application, which the user will be redirected to if error comes during signing the folder in the embedded signing view.
Action
Write
Catch Raw Hook
Wait for a new POST, PUT, or GET to a Zapier URL. Gives the request body unparsed (max 2 MB) and also includes headers.
Trigger
Instant
Try It

- MethodRequired
  The HTTP method we'll use to perform the request.
- URLRequired
  Any URL with a querystring will be re-encoded properly.
- Data Pass-Through?
  If yes, request data below will be overridden with the raw data from the previous step (you are still responsible for headers though, like Content-Type). Defaults to no.
- Data
  Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data Content-Type. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.
- Unflatten
  By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.
- Basic Auth
  A pipe (|) separated username, password combo for standard HTTP authentication.
- Headers
  Key, value pairs to be added as headers in all requests.
Action
Write
- URLRequired
  Any URL with a querystring will be re-encoded properly.
- Payload Type
  Pay special attention to the proper mapping of the data below.
- Data
  These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.
- Wrap Request In Array
  Wraps the request in an array if that is something the service requires.
- File
  A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.
- Unflatten
  By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.
- Basic Auth
  A pipe (|) separated username, password combo for standard HTTP authentication.
- Headers
  Key, value pairs to be added as headers in all requests.
Action
Write

Document Deleted
Triggers when a Document has been Deleted from your Account. Available for our Paid or Trial Business Premium accounts.
Trigger
Instant
Try It
Document Sent
Triggers when a Document has been sent for signature. Available for our Paid or Trial Business Premium accounts.
Trigger
Instant
Try It
Document Viewed
Triggers whenever a signer has opened and viewed the Document for the first time. You get a separate trigger when each Party Views the Document. Available for our Paid or Trial Business Premium accounts.
Trigger
Instant
Try It
- URLRequired
  This should return a list of dictionaries of content type JSON in reverse chronological order. For example: [{"id":1234},{"id":1235}]
- Key
  If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)
- Deduplication Key
  Zapier deduplicates the array we see each poll against the id key. If the id key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with id in it otherwise we will raise an error.
- Xpath
  If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!
- Basic Auth
  A pipe (|) separated username, password combo for standard HTTP authentication.
- Headers
  Key, value pairs to be added as headers in all requests.
Trigger
Scheduled
Try It
- Pick off a Child Key
  By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given {"contact": {"name": "Mike"}}, add "contact" here to only return {"name": "Mike"}. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.
Trigger
Instant
Try It
- URLRequired
  We recommend not putting any query string arguments in the URL (use "Query String Params" below).
- Query String Params
  These params will be URL-encoded and appended to the URL when making the request. Note: If you specify nothing for this field, we will automatically encode and include every field from the previous step in the query string. If you don't want this, use the "Custom Request" action.
- Send As JSON
  If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.
- JSON key
  Only used if As JSON.
- Unflatten
  By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.
- Basic Auth
  A pipe (|) separated username, password combo for standard HTTP authentication.
- Headers
  Key, value pairs to be added as headers in all requests.
Action
Write
- URLRequired
  Any URL with a querystring will be re-encoded properly.
- Payload Type
  Pay special attention to the proper mapping of the data below.
- Data
  These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.
- Wrap Request In Array
  Wraps the request in an array if that is something the service requires.
- File
  A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.
- Unflatten
  By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.
- Basic Auth
  A pipe (|) separated username, password combo for standard HTTP authentication.
- Headers
  Key, value pairs to be added as headers in all requests.
Action
Write

How Foxit eSign + Webhooks by Zapier Integrations Work

Step 1: Authenticate Foxit eSign and Webhooks by Zapier.
30 seconds
Step 2: Pick one of the apps as a trigger, which will kick off your automation.
15 seconds
Step 3: Choose a resulting action from the other app.
15 seconds
Step 4: Select the data you want to send from one app to the other.
2 minutes
That’s it! More time to work on other things.

Connect apps

Connect Foxit eSign + Webhooks by Zapier

About Foxit eSign

Foxit eSign is an end-to-end cloud-based esignature solution that is cost-effective, comprehensive, and legally binding with Templates, Bulk Signing, Online Forms, APIs. Foxit eSign also offers convenience of signing from within Foxit Desktop and Cloud PDF.

Related categories

Signatures

About Webhooks by Zapier

Webhooks simply POST data (or JSON) to a specific URL every time we see something new. Webhooks can also accept data (or JSON) to kick off a workflow in Zapier.

Related categories

Get started for free

You can't add more hours to the day. Zapier is the next best thing.

By signing up, you agree to Zapier's terms of service and privacy policy.

Foxit eSign + Webhooks by Zapier Integrations

How to connect Foxit eSign + Webhooks by Zapier

Connect your apps and automate workflows

Document Cancelled

Document Executed

Document Signed

Create Folder From Template

TemplateRequired

Folder Name

First NameRequired

Last NameRequired

EmailRequired

PermissionRequired

SequenceRequired

In Person Administrator Email

Allow Signer to Correct Name

Sender Email

Enable Signing Sequence

Send Now

Enable In Person Signing

Static Recipients

Static Documents

Send Success URL

Send Error URL

Sign Success URL

Sign Decline URL

Sign Later URL

Sign Error URL

Catch Raw Hook

Custom Request

MethodRequired

URLRequired

Data Pass-Through?

Data

Unflatten

Basic Auth

Headers

POST

URLRequired

Payload Type

Data

Wrap Request In Array

File

Unflatten

Basic Auth

Headers

Document Deleted

Document Sent

Document Viewed

Retrieve Poll

URLRequired

Key

Deduplication Key

Xpath

Basic Auth

Headers

Catch Hook

Pick off a Child Key

GET

URLRequired

Query String Params

Send As JSON

JSON key

Unflatten

Basic Auth

Headers

PUT

URLRequired

Payload Type

Data

Wrap Request In Array

File

Unflatten

Basic Auth

Headers

About Foxit eSign

Related categories

About Webhooks by Zapier

Related categories

Get started for free