This PDF was generated automatically.
", "filename": "document.pdf" } ``` ### Response handling Configure the response settings: | Setting | Value | |---------|-------| | Parse response | `Yes` | --- ## Configure the HTTP module ### 1. Add the HTTP module After your trigger module, click **+** and search for "HTTP": 1. Select **HTTP** 2. Choose **Make a request** 3. The configuration panel will open ### 2. Configure the URL and method | Field | Value | |-------|-------| | URL | `https://api.pdf-mcp.io/htmlToPdf` | | Method | `POST` | ### 3. Add headers Click **Add a header** and configure: | Name | Value | |------|-------| | Authorization | `Bearer YOUR_API_KEY` | ### 4. Configure the body | Field | Value | |-------|-------| | Body type | `Raw` | | Content type | `JSON (application/json)` | ### 5. Add the request content In the **Request content** field, enter your JSON payload: ```json { "html": "Generated automatically.
", "filename": "document.pdf" } ``` ### 6. Configure response handling Expand **Show advanced settings**: | Setting | Value | |---------|-------| | Parse response | `Yes` (if you need JSON response) or `No` (for binary PDF) | ### 7. Test the module Select **Run once**. A successful request puts the PDF data in the module output. --- ## Module settings to copy Enter these settings in the Make HTTP module: ### HTML to PDF module **URL:** ``` https://api.pdf-mcp.io/htmlToPdf ``` **Method:** `POST` **Headers:** ``` Authorization: Bearer YOUR_API_KEY ``` **Body type:** `Raw` **Content type:** `JSON (application/json)` **Request content:** ```json { "html": "Your content here.
", "css": "@page { size: A4; margin: 2cm; }", "filename": "document.pdf" } ``` --- ## Dynamic HTML with Make variables Use Make's variable mapping to create dynamic PDFs from your trigger data. ### Variables in JSON Make uses double curly braces `{{}}` for variable mapping. In the JSON editor: ```json { "html": "Customer: {{1.customer_name}}
Amount: ${{1.amount}}
", "filename": "invoice-{{1.invoice_number}}.pdf" } ``` The number before each field, such as `1.`, is the module's position in the scenario. ### Form response example If your trigger is a webhook or form submission: ```json { "html": "Name: {{1.name}}
Email: {{1.email}}
Message: {{1.message}}
Submitted: {{formatDate(now; \"MMMM D, YYYY\")}}
", "filename": "submission-{{1.submission_id}}.pdf" } ``` ### Invoice example For e-commerce or payment triggers: ```json { "html": "Customer: {{1.customer_name}}
Email: {{1.customer_email}}
| Description | Amount |
|---|---|
| {{1.product_name}} | ${{1.amount}} |
Total: ${{1.amount}}
", "css": "@page { size: A4; margin: 2cm; } body { font-family: Arial, sans-serif; }", "filename": "invoice-{{1.invoice_number}}.pdf" } ``` ### Certificate example For course completions or achievements: ```json { "html": "This is to certify that
{{1.recipient_name}}
has successfully completed
{{1.course_name}}
Date: {{formatDate(now; \"MMMM D, YYYY\")}}
", "css": "@page { size: landscape; margin: 2cm; }", "filename": "certificate-{{1.recipient_name}}.pdf" } ``` --- ## Scenario examples ### 1. Webhook to PDF ``` [Webhooks] → [HTTP: Generate PDF] → [Email: Send Attachment] ``` **Trigger:** Webhooks - Custom webhook receives data **Action 1:** HTTP - Make a request to pdf-mcp **Action 2:** Email - Send with PDF attachment ### 2. Google Sheets to PDF report ``` [Google Sheets: Watch Rows] → [HTTP: Generate PDF] → [Google Drive: Upload] ``` **Trigger:** Google Sheets - Watch New Rows **Action 1:** HTTP - Generate PDF from row data **Action 2:** Google Drive - Upload file to folder ### 3. Stripe payment to invoice ``` [Stripe: Watch Events] → [HTTP: Generate Invoice PDF] → [Dropbox: Upload] ``` **Trigger:** Stripe - Watch Events (payment completed) **Action 1:** HTTP - Generate invoice PDF **Action 2:** Dropbox - Upload File ### 4. Airtable record to certificate ``` [Airtable: Watch Records] → [HTTP: Generate Certificate] → [Gmail: Send] ``` **Trigger:** Airtable - Watch Records **Action 1:** HTTP - Generate certificate PDF **Action 2:** Gmail - Send email with attachment ### 5. Scheduled report ``` [Schedule] → [Database Query] → [HTTP: Generate Report] → [Slack: Post Message] ``` **Trigger:** Schedule - Run at specific time **Action 1:** Query your database for data **Action 2:** HTTP - Generate PDF report **Action 3:** Slack - Post link to report --- ## API endpoints Configure your HTTP module with these endpoints: | Endpoint | Method | Description | |----------|--------|-------------| | `/htmlToPdf` | POST | Convert HTML to PDF | | `/textToPdf` | POST | Convert plain text to PDF | | `/imageToPdf` | POST | Convert images to PDF | | `/pdfToImage` | POST | Convert PDF pages to images | | `/extractText` | POST | Extract text from PDF | | `/extractPages` | POST | Extract specific pages | | `/mergePdfs` | POST | Combine multiple PDFs | | `/pageCount` | POST | Get PDF page count | See the [API reference](https://pdf-mcp.io/docs/api-reference) for request and response details. --- ## cURL examples Test the API directly before configuring Make: ### Basic HTML to PDF request ```bash curl -X POST https://api.pdf-mcp.io/htmlToPdf \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "html": "Generated from Make scenario.
" }' \ --output document.pdf ``` ### Styled invoice ```bash curl -X POST https://api.pdf-mcp.io/htmlToPdf \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "html": "| Item | Amount |
|---|---|
| Service Fee | $99.00 |
Total: $99.00
", "css": "@page { size: A4; margin: 2cm; } body { font-family: Arial, sans-serif; } table { width: 100%; border-collapse: collapse; } th, td { border: 1px solid #ddd; padding: 8px; }", "filename": "invoice-12345.pdf" }' \ --output invoice-12345.pdf ``` ### Text to PDF ```bash curl -X POST https://api.pdf-mcp.io/textToPdf \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "text": "Meeting Notes\n\nDate: January 15, 2025\n\n1. Project status review\n2. Timeline discussion\n3. Next steps", "filename": "meeting-notes.pdf" }' \ --output meeting-notes.pdf ``` --- ## MCP clients > For an MCP client, enter the hosted Streamable HTTP URL directly. There is no pdf-mcp package or local server to install. See the verified [MCP client setup guide](https://pdf-mcp.io/docs/mcp-server). --- ## Handle the response The HTTP module returns the PDF as binary data. Map that output into the next module that needs the file. ### Save to cloud storage Connect to Google Drive, Dropbox, OneDrive, or other storage modules: 1. Add a storage module after the HTTP module 2. Map the `data` output from the HTTP module to the file content 3. Specify the filename and destination folder ### Send by email Use Gmail, Outlook, or other email modules: 1. Add an email module after the HTTP module 2. In the attachment field, map the HTTP module's response data 3. Set the attachment filename ### Download locally during testing Use the **Make DevTool** browser extension to download files during testing. ### Store in a database Encode the binary data as base64 and store in your database if needed. --- ## Work with binary data Make handles binary data through its data bundles. To work with PDF files: ### Pass data to a storage module Most storage modules (Google Drive, Dropbox, etc.) accept binary data directly: 1. In the file content field, select the `data` output from the HTTP module 2. Specify the filename with `.pdf` extension ### Pass data to an email attachment Email modules typically accept binary attachments: 1. Map the HTTP response body to the attachment data 2. Set the filename (e.g., `document.pdf`) 3. Set the content type to `application/pdf` ### Convert to base64 If you need base64 encoding, use Make's `toString` function: ``` {{toString(HTTP_MODULE.data; "base64")}} ``` --- ## Error handling Make can route failures through error handlers. ### Common status codes | Code | Description | Solution | |------|-------------|----------| | 200 | Success | PDF generated successfully | | 401 | Unauthorized | Check your API key in headers | | 402 | Payment Required | Add credits to the account | | 403 | Forbidden | Verify API key permissions | | 400 | Bad Request | Check your request body format | | 500 | Server Error | Review HTML syntax or contact support | ### Add an error handler 1. Right-click on the HTTP module 2. Select **Add error handler** 3. Choose the handler type: - **Resume**: Continue with default value - **Rollback**: Undo previous operations - **Commit**: Save completed operations - **Ignore**: Skip errors silently ### Route success and error paths Add a Router after the HTTP module to handle success and error cases separately: ``` [HTTP Module] → [Router] ├── Route 1: Status = 200 → [Continue with PDF] └── Route 2: Status != 200 → [Send Alert/Log Error] ``` Configure the router filters: - Route 1 filter: `{{HTTP_MODULE.statusCode}} = 200` - Route 2 filter: `{{HTTP_MODULE.statusCode}} != 200` --- ## Troubleshooting ### PDF is empty or not generated - Verify your API key is correct and has credits - Check that the `html` field contains valid HTML - Ensure the JSON is properly formatted - Test with a simple HTML string first ### Authentication errors (401/403) - Check the Authorization header format: `Bearer YOUR_API_KEY` - Ensure there's a space between "Bearer" and your key - Verify your API key hasn't been revoked ### Insufficient credits (402) - Check your credit balance in the dashboard ### Module timeout - Large or complex HTML may take longer to process - Increase the timeout in advanced settings (Settings > Timeout) - Simplify your HTML template - Use inline styles instead of external resources ### Invalid JSON errors - Validate your JSON in the Make editor - Escape special characters in strings (use `\"` for quotes) - Check for trailing commas or missing brackets - Use Make's JSON functions for complex data ### Variable mapping issues - Verify module numbers match your scenario layout - Use the variable picker to ensure correct paths - Test each module individually with hardcoded values - Check that trigger data contains expected fields ### Binary data not recognized - Ensure **Parse response** is set correctly - Some downstream modules need specific content types - Try base64 encoding for problematic integrations --- ## Implementation notes ### Performance - Keep HTML simple for faster generation - Use inline CSS instead of external stylesheets - Compress images before including them - Avoid unnecessary complexity in templates ### Reliability - Test scenarios thoroughly before activating - Use Make's execution history to debug issues - Set up error notifications for critical scenarios - Schedule non-urgent operations during off-peak hours ### Security - Never expose your API key in shared scenarios - Use Make's connection feature for secure credential storage - Limit scenario sharing to trusted team members - Review data exposure in public scenarios ### Credit usage - Use filters to only generate PDFs when necessary - Batch similar operations with iterators - Monitor API credit usage regularly - Set up alerts for high usage ### Organization - Name your modules descriptively - Add notes to complex scenarios - Group related modules with labels - Use folders to organize scenarios --- ## Make function reference These Make functions can prepare values for PDF requests: | Function | Description | Example | |----------|-------------|---------| | `formatDate` | Format dates | `{{formatDate(now; "YYYY-MM-DD")}}` | | `toString` | Convert to string | `{{toString(1.amount)}}` | | `replace` | Replace text | `{{replace(1.html; "\n"; "