eSignatures.io #3857

[lcaresia]

Oficial API don't have a way to register a webhook, so this PR only have the action.

Actions

• Create Contract

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
pipedream-docs	✅ Ready (Inspect)	Visit Preview	Sep 2, 2022 at 9:06PM (UTC)
pipedream-docs-redirect-do-not-edit	✅ Ready (Inspect)	Visit Preview	Sep 2, 2022 at 9:06PM (UTC)

[dylburger]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible

[michelle0927]

Looks good!

[vunguyenhung]

Hi everyone, all test cases are passed! Ready for release!

Test report
eSignatures.pdf

---

@lcaresia on another note, I think we might need to contact with eSignatures team to get their help on the triggers right?

[lcaresia]

@lcaresia on another note, I think we might need to contact with eSignatures team to get their help on the triggers right?

@vunguyenhung It's possible, you can use the custom webhook field when is creating the contract, but you can't create a external webhook using the oficial API.

[lcaresia]

/approve

[vunguyenhung]

Hello @lcaresia, thanks for your information! I think we can merge this. I've created another Github issue here to track the remaining triggers #3928.