Overview
Foxit eSign is an electronic signature platform used by organizations to send, sign, and manage legally binding documents and signing workflows.
The Alchemer integration with Foxit eSign supports automated workflow initiation based on events from a Foxit eSign webhook channel. The Alchemer → Foxit eSign Workflow Initiator allows Alchemer to receive webhook events from Foxit eSign (such as a document being signed or a signing folder being completed) and trigger a workflow run for each event, automatically passing along signer and document details without manual intervention.
Common uses for the Alchemer Foxit eSign integration
- Trigger a workflow when a document or envelope is signed in Foxit eSign
- Notify internal stakeholders when a signing folder is completed or executed
- Automatically enroll signers in follow-up communications once signing is complete
- Kick off downstream system updates when e-signature events occur
- Route signer and document data from Foxit eSign into other business systems
What can the Alchemer Foxit eSign integration do?
You will need
- A Foxit eSign webhook channel. More details in the authentication how-to guide.
- An Alchemer plan that includes integrations with Workflow 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 | Initiate from Foxit webhook channel
You will need:
- A Foxit eSign webhook channel you can configure to send events to Alchemer. More details in the authentication how-to guide.
- Any additional custom fields you want Foxit eSign to include in its webhook payload, beyond the fields provided by default.
Configure the action
- Open your workflow in Workflow Builder.
- On the Select Initiator pop up select the Foxit eSign initiator.
- Select Foxit eSign | Initiate from Foxit webhook channel.
- Foxit eSign | Webhook URL: Alchemer generates a unique URL for this action. Copy this URL and enter it into the corresponding webhook channel configuration in Foxit eSign.
- Foxit eSign | Custom Fields: This initiator is pre-populated with the fields Foxit eSign sends by default, so you do not need to define them yourself:
- Party 1 firstName
- Party 1 lastName
- Party 1 emailId
- Party 1 dialingCode
- Party 1 mobileNumber
- Foxit eSign | Custom Headers (optional): Add key/value header pairs if you want to secure the webhook so it only triggers when the specified headers are present.
- Foxit eSign | IP Whitelist (optional): Enter the IP address(es) that requests should originate from. Incoming requests must match one of these addresses to be accepted.
- Foxit eSign | Basic Authentication (optional): Enter a username and password if you want to require basic authentication on incoming requests.
- Save the action.
- In Foxit eSign, ensure the webhook channel's trigger event is set to the event you want to initiate on (for example, on folder_signed vs. on folder_executed), and that its security settings (headers, IP whitelist, and/or basic authentication) match what you configured above.
- Activate the webhook channel in Foxit eSign.
- Publish and activate the Alchemer workflow.
Status codes
- 200: Successfully triggered a workflow run for the Foxit eSign webhook event
- 400: The external integration returned an error
Testing and Troubleshooting
Testing and Validation
How to test
- Trigger a qualifying event in Foxit eSign (for example, complete a signing) and monitor individual runs in the Monitor tab.
- Click on each run to view the metadata received from the webhook.
How to verify results
- Set a send email action to yourself with action metadata included.
- Verify that the expected signer and document data from Foxit eSign generated a workflow run.
Monitoring Integration Activity
Where to find logs
- Go to Monitor.
- Check the individual workflow steps.
What logs display
- Inputs received from the Foxit eSign webhook channel
- Workflow output or returned status
Troubleshooting
Authentication issues
- Custom Headers, IP Whitelist, or Basic Authentication values in Alchemer don't match the webhook channel's security settings in Foxit eSign
- Missing permissions or an inactive webhook channel in Foxit eSign
Foxit eSign-specific issues
- Webhook channel trigger event is set to an event other than the one you intended (for example, folder_signed vs. folder_executed)
- Webhook channel is not activated in Foxit eSign
- Custom fields sent by Foxit eSign don't match the fields configured in the action
API errors
- Foxit eSign validation failures
- Endpoint or runtime errors
FAQs
What permissions do I need?
Integration Manager in Alchemer and the ability to configure webhook channels in Foxit eSign.
Integration Manager in Alchemer and the ability to configure webhook channels in Foxit eSign.
When does the integration run?
Whenever Foxit eSign sends a webhook event for the trigger you configured on the webhook channel.
Whenever Foxit eSign sends a webhook event for the trigger you configured on the webhook channel.
Do I need to configure the default signer fields myself?
No. Party 1 firstName, lastName, emailId, dialingCode, and mobileNumber are included automatically. Only add custom fields for data beyond these defaults.
No. Party 1 firstName, lastName, emailId, dialingCode, and mobileNumber are included automatically. Only add custom fields for data beyond these defaults.
Why isn't my workflow triggering?
Check the Monitor tab for authentication mismatches, an inactive webhook channel, or an incorrectly configured trigger event in Foxit eSign.
Check the Monitor tab for authentication mismatches, an inactive webhook channel, or an incorrectly configured trigger event in Foxit eSign.
What if I need additional functionality?
Contact Alchemer Support for enhancement requests.
Contact Alchemer Support for enhancement requests.
