Generating PDFs - best practice for dealing with limitations

At the moment, the specific function you are looking for is not available.

I suggest you include this idea in our suggestions forum! You can follow the progress of all the suggestions and vote for the ones that interest you the most.

Remember that our product development is defined annually, so some suggestions may take a while to be implemented or made feasible.

Hi Rodrigo, I’ve stopped logging feature requests. They never come to anything and when I look at feature requests from other users much the same happens. The Pipefy Dev team rarely address bugs either. As a business owner I need to spend my time productively

@mark-theotcentre , I recently implemented a solution for a client that addresses these issues.

To solve these limitations, I used an integration with Make.

The final PDF result is 100% customizable, and it also allows for the use of connected cards and much more.

Here is an example of a PDF generated by Pipefy with my integration:

The information in the document is filled out based on several fields connected in tables and also through connected cards (products).

All calculations are also made during integration.

Hi @Lucas Democh that’s interesting. I’m a big user of make and have extensive knowledge of API’s & integrations incl the Pipefy APIs.

Can you explain in a bit more detail how you’re approaching/achieving this?

THanks for any help

Mark

Hi @mark-theotcentre,

I'll be honest with you.

I developed this scenario for this client and he didn't pay me (a deadbeat with a CEO position).

Since I invested a lot of time in developing it, I'm willing to negotiate the blueprint + adaptation (if you need it).

For free, I can give you general guidelines so that you can achieve the same result:
- Use the trigger of your choice on the parent card (which contains all the connections you need to use in the PDF construction).
- Use the card query to search for all the details, including the connected cards.
- Use queries to the subsequent cards and tables to pull data from the connected records.
- Build the PDF structure in HTML for greater flexibility, using LOOP to fill in connection data (products example).
- After finishing, use the HTML to PDF transformation.
- If you want the PDF to be attached to the card, send an email with the generated PDF to the card that generated the document (card email).