Overview

Foxit eSign is an electronic signature platform used by organizations to send, sign, and manage legally binding documents and signing workflows.

Common uses for the Alchemer Foxit eSign integration

• Automatically send a document out for signature as part of a workflow
• Use workflow data to populate the signing party's contact information
• Kick off e-signature workflows without manual data entry
• Route different records to different Foxit eSign templates based on workflow logic
• Reduce turnaround time between a workflow trigger and a signature request

What can the Alchemer Foxit eSign integration do?

• Send template for signing

You will need

• Foxit eSign OAuth authentication (Client ID, Client Secret, and Hostname). More details in the authentication how-to guide.
• An Alchemer plan that includes integrations and the Integration Manager permission enabled.
  • Contact us if you are unsure if your plan includes integrations.

Setup Alchemer Foxit eSign integration in workflow

Foxit eSign | Send template for signing

You will need:

• Foxit eSign OAuth authentication (Client ID, Client Secret, and Hostname). More details in the authentication how-to guide.
• Workflow fields containing the signing party's email address and first name, at minimum

Configure the action

1. Open your workflow in Workflow builder.
2. On the right side, drag and drop the Foxit eSign connection where you want the action to trigger.
3. In the connection box, click the pencil icon in the top-right corner.
4. Select Foxit eSign | Send template for signing.
5. Foxit eSign | Authentication: Select an existing authentication or create a new one using your Client ID, Client Secret, and Hostname.
6. Foxit eSign | Template: Choose the Foxit eSign template you want to send out for signing, then confirm your selection.
7. Foxit eSign | Party/Signer Info: Map the Alchemer fields you want to use to the corresponding Foxit fields for the signing party.
   1. Note: Email, First Name, and Last Name must be mapped. All other signer fields are optional.
8. Save the action.

Status codes

• 200: Successfully sent the Foxit eSign template out for signing
• 400: The external integration returned an error

Testing and Troubleshooting

Testing and Validation

How to test

• Trigger the workflow and monitor individual runs in the Monitor tab.
  • Click into individual workflow runs to see input/output metadata.
• Confirm the signing party receives the Foxit eSign template.
• Use metadata values returned to verify success or help debug issues.

How to verify results

• Check the signing status of the document in Foxit eSign.
• Ensure the signing party's information matches workflow expectations.

Monitoring Integration Activity

Where to find logs

• Go to Results → Monitor.
• Select the integration step you want to inspect.

What logs display

• Input/Output

Troubleshooting

Authentication issues

• Incorrect or expired Client ID, Client Secret, or Hostname
• Missing permissions in Foxit eSign

Mapping errors

• Email or First name for the signing party not mapped
• Incorrectly formatted signer field values

Template errors

• Selected Foxit eSign template no longer exists or was not confirmed

API errors

• Foxit eSign validation failures
• Endpoint or runtime errors

FAQs