[SOURCE] eSignatures.io webhooks

[vunguyenhung]

App

eSignatures.io

Triggers

Contract Sent to Signer Contract Signed by All Contract Signed by Signer Delivery Failed Mobile Number Update Request by Signer

Context

Per @lcaresia mentioned here, eSignatures doesn't have an official way to register Pipedream webhooks. This means we couldn't implement the triggers required. I think we need to contact with eSignatures on this

[dylburger]

Thanks for the request! We've added this to our integrations backlog, and we'll update this ticket with progress.

[sergioeliot2039]

Or perhaps sources could be implemented as polled based, instead of webhooks based (like Reddit's sources).

[vunguyenhung]

Hello @lcaresia, sorry could you advice is it possible to do polling for eSignatures as @sergioeliot2039 commented? I suspect that in order to do pooling for the triggers, eSignature needs to have APIs for us to fetch the respective data, which might not be the case https://esignatures.io/docs/api

[lcaresia]

@vunguyenhung We don't be by polling becasue Esignatures don't have a way to get a list of contracts.

[vunguyenhung]

@sergioeliot2039 boss, as @lcaresia explained, we couldn't do polling since eSignatures doesn't provide API to do that. I think we need to contact them for registering our webhook 🙏

[dylburger]

Thanks for the request! We've added this to our integrations backlog, and we'll update this ticket with progress.

[sergioeliot2039]

Got it, thanks for looking into it @lcaresia and @vunguyenhung

I have removed the "added to app backlog" because eSignatures is integrated -- https://pipedream.com/apps/esignatures-io

However, triggers / sources for this issue are triaged under Component (Source and Action) backlog -- https://github.com/PipedreamHQ/pipedream/projects/1#card-84715213

Cheers

[dannyroosevelt]

I sent an note to their team