[Components] fynk

[pipedream-component-development]

URLs
• https://app.fynk.com/v1/docs#/

Actions
create-contract-from-template
Prompt
Create a new contract from an existing template. Requires Contract Write & Template Read permissions to retrieve the template ID.

upload-signed-contract
Prompt
Upload a signed contract as a PDF document to Fynk for storage and tracking.

update-contract-metadata
Prompt
Update contract metadata or dynamic field values to reflect changes in contract details.

update-contract-party
Prompt
Modify or replace contract party information to ensure accurate representation of stakeholders.

move-contract-stage
Prompt
Move a contract to the review or signing stage within Fynk’s workflow for progression.

[sergio-eliot-rodriguez]

Currently completed actions
create-contract-from-template
update-contract-metadata
update-contract-party
move-contract-stage,

troubleshooting upload-signed-contrat-action, may reach out to fynk support

[sergio-eliot-rodriguez]

I verified that uploading a contract to the URL provided by Fynk fails with a 501 error when attempted from Pipedream:

I tested both approaches — as a standalone component and as a custom Node.js code step in the Pipedream workflow builder. My suspicion is that the issue may be related to extra headers added by the underlying AWS worker.

Using plain axios also fails, though it doesn’t expose the same level of detail as axios from @pipedream/platform:

For comparison, the same sequence works correctly in Postman:

Step 1: Request the endpoint from Fynk to obtain a presigned URL for contract upload:

Step 2: Use the presigned URL provided by Fynk to upload the contract:

Since this behavior is not an issue on Fynk’s side, I’ll continue investigating internally.