How to connect PDFMonkey and SOS Inventory
Create a New Scenario to Connect PDFMonkey and SOS Inventory
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a PDFMonkey, triggered by another scenario, or executed manually (for testing purposes). In most cases, PDFMonkey or SOS Inventory will be your first step. To do this, click "Choose an app," find PDFMonkey or SOS Inventory, and select the appropriate trigger to start the scenario.

Add the PDFMonkey Node
Select the PDFMonkey node from the app selection panel on the right.


PDFMonkey

Configure the PDFMonkey
Click on the PDFMonkey node to configure it. You can modify the PDFMonkey URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the SOS Inventory Node
Next, click the plus (+) icon on the PDFMonkey node, select SOS Inventory from the list of available apps, and choose the action you need from the list of nodes within SOS Inventory.


PDFMonkey
⚙
SOS Inventory

Authenticate SOS Inventory
Now, click the SOS Inventory node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your SOS Inventory settings. Authentication allows you to use SOS Inventory through Latenode.
Configure the PDFMonkey and SOS Inventory Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the PDFMonkey and SOS Inventory Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
SOS Inventory
Trigger on Webhook
⚙

PDFMonkey
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring PDFMonkey, SOS Inventory, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the PDFMonkey and SOS Inventory integration works as expected. Depending on your setup, data should flow between PDFMonkey and SOS Inventory (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect PDFMonkey and SOS Inventory
SOS Inventory + PDFMonkey + Airtable: When a new sales order is created in SOS Inventory, generate a product specification sheet PDF using PDFMonkey, then log the information in an Airtable database.
SOS Inventory + PDFMonkey + WooCommerce: When stock is low, generate a PDF catalog using PDFMonkey and create product offers in WooCommerce.
PDFMonkey and SOS Inventory integration alternatives

About PDFMonkey
Use PDFMonkey in Latenode to automate document creation from templates. Populate PDFs with data from any app (CRM, database, etc.) via API. Latenode lets you trigger PDF generation based on events, archive documents, and send them automatically. Simplify reporting and document workflows with no-code or custom code.
Similar apps
Related categories
About SOS Inventory
Sync SOS Inventory with Latenode to automate stock updates and order processing. Connect your inventory data to accounting, e-commerce, or shipping platforms. Build visual workflows to trigger actions based on inventory levels or sales data. Use no-code tools or custom scripts to tailor the flow, avoiding manual data entry and ensuring real-time accuracy.
Related categories
See how Latenode works
FAQ PDFMonkey and SOS Inventory
How can I connect my PDFMonkey account to SOS Inventory using Latenode?
To connect your PDFMonkey account to SOS Inventory on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select PDFMonkey and click on "Connect".
- Authenticate your PDFMonkey and SOS Inventory accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically generate invoices upon shipment in SOS Inventory?
Yes! Latenode lets you trigger PDFMonkey to create invoices whenever SOS Inventory marks an order shipped. Benefit from automated document generation, reducing manual data entry.
What types of tasks can I perform by integrating PDFMonkey with SOS Inventory?
Integrating PDFMonkey with SOS Inventory allows you to perform various tasks, including:
- Automatically generate packing slips when a sales order is created.
- Create customized invoices with real-time inventory data.
- Generate shipping labels directly from updated inventory levels.
- Archive signed delivery confirmations with corresponding inventory records.
- Update product spec sheets automatically based on inventory changes.
How easily can I customize the PDF templates within Latenode?
Latenode allows robust PDF template customization via no-code blocks, JavaScript, or AI, giving unparalleled flexibility for tailored documents.
Are there any limitations to the PDFMonkey and SOS Inventory integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex conditional logic in PDF templates may require JavaScript knowledge.
- High-volume PDF generation can be subject to PDFMonkey's rate limits.
- SOS Inventory custom fields might need specific mapping configurations.