Softr

​

Prerequisites

• A DocsAutomator account (free trial available)
• A Softr account

​

Setting Up the Integration

​

Step 1: Create a DocsAutomator Automation

1. Log in to your DocsAutomator account
2. Click New Automation from the dashboard
3. Select Softr as your data source
4. Choose or create your Google Doc template
5. Configure your output settings (PDF, email, Google Drive folder, etc.)
6. Save the automation

​

Step 2: Get Your API Key

1. In DocsAutomator, go to Settings → API Key
2. Copy your API key—you’ll need this for Softr

​

Step 3: Connect DocsAutomator in Softr

1. Log in to Softr Studio
2. Open your application
3. Go to Settings → Integrations
4. Find DocsAutomator in the third-party integrations list
5. Paste your API key and save

​

Creating a Workflow with DocsAutomator

​

Step 1: Create a New Workflow

1. In Softr Studio, go to Workflows
2. Click Create Workflow
3. Choose a trigger for your workflow:

• Softr Databases – Trigger when records are created or updated in Softr’s native databases
• Softr Apps – Trigger from events in your Softr app (form submissions, button clicks, etc.)

• Webhook – Trigger from external services (Pro plan)
• One-time schedule – Run once at a specific date/time
• Recurring schedule – Run on a recurring basis (daily, weekly, monthly)

• Airtable – Trigger when Airtable records are created or updated
• Google Sheets – Trigger from Google Sheets changes
• Gmail – Trigger from incoming emails
• Notion – Trigger from Notion database changes

​

Step 2: Add the DocsAutomator Action

1. After your trigger, click the + button to add an action
2. Select DocsAutomator from the integrations list
3. Choose Create document

​

Step 3: Configure the Action

• Account – Select your connected DocsAutomator account
• Automation ID – Choose which DocsAutomator automation to use
• Document Name – Set a dynamic name for the generated document (optional)
• JSON body for placeholders – Map your data to template placeholders

​

Step 4: Map Your Data

{
  "Start_Date": "{{trigger.fields['FIELD_ID']}}",
  "Project_Name": "{{trigger.fields['FIELD_ID']}}",
  "Project_Manager": "{{trigger.fields['FIELD_ID']}}"
}

• Trigger data – Fields from the record or event that triggered the workflow
• Previous steps – Output from earlier workflow actions (Find records, Run code, etc.)
• Static values – Fixed text or numbers

​

Step 5: Test Your Workflow

1. Click Test Workflow in Softr
2. Select a sample record or provide test data
3. Verify the document was generated correctly in DocsAutomator’s Run History

​

Working with Line Items

​

Passing Line Items

{
  "customer_name": "Acme Corp",
  "invoice_number": "INV-001",
  "line_items_1": [
    {
      "item_name": "Consulting",
      "quantity": "10",
      "unit_price": "150",
      "line_total": "1500"
    },
    {
      "item_name": "Development",
      "quantity": "20",
      "unit_price": "200",
      "line_total": "4000"
    }
  ]
}

​

Line Items from Related Records

1. Find multiple records – Fetch the related records
2. Run custom code – Format the records into a line items array
3. Create document – Pass the formatted array to DocsAutomator

const input = inputData['tasks']
const arr = input.map(task => {
  return {
    task: task.fields['fBKYw'],        // Field ID for Task Name
    description: task.fields['75Q7j']  // Field ID for Description
  }
})
return arr

{
  "Project_Name": "{{trigger.fields.Project name}}",
  "line_items_1": "{{code_step.body}}"
}

​

Including Images

{{image_logo}}
{{image_product}}
{{image_signature}}

{
  "image_logo": "{{trigger.fields['FIELD_ID']}}",
  "image_product": "{{trigger.fields['FIELD_ID']}}"
}

​

Formatting Numbers, Dates, and Checkboxes

​

Common Use Cases

​

Invoice with Line Items

1. Trigger: Softr Databases – Record meets conditions (Status = “Ready to Invoice”)
2. Find multiple records – Fetch invoice line items linked to the order
3. Run custom code – Format line items into an array
4. Create document – Generate invoice with line items
5. Update record – Save the PDF URL back to the order record

​

Project Summary Report

1. Trigger: Softr Databases – Record meets conditions
2. Find multiple records – Fetch tasks linked to the project
3. Run custom code – Format tasks into line items
4. Create document – Generate project summary
5. Update record – Save document URL to project record

​

Contract on Status Change

1. Trigger: Softr Databases – Record meets conditions (Stage = “Contract”)
2. Create document – Generate contract from deal data
3. Update record – Save contract URL to deal record

​

Scheduled Reports

1. Trigger: Recurring schedule – Weekly or monthly
2. Find multiple records – Fetch records for the report period
3. Run custom code – Aggregate and format data
4. Create document – Generate the report
5. Send email or notification – Deliver to stakeholders

​

Troubleshooting

​

Automation Not Appearing in Dropdown

• Verify your automation uses Softr as the data source in DocsAutomator
• Check that your DocsAutomator account is connected in Softr’s integration settings
• Try disconnecting and reconnecting the DocsAutomator integration

​

Document Not Generating

• Check Run History: Go to DocsAutomator → Run History to see error details
• Verify JSON Body: Ensure your JSON is valid and all placeholder names match your template exactly
• Test the Create document step: Use Softr’s Testing tab to run the action with sample data

​

Data Not Appearing in Document

• Check JSON Mapping: Verify the correct fields are referenced in the JSON body
• Test with Static Values: Replace dynamic references with static text to isolate the issue
• Check Data Types: Dates and numbers may need specific formatting
• Verify Previous Steps: If using data from Find records or Code steps, test those steps first

​

Line Items Not Working

• Use correct key: Line items must use line_items_1 (with underscores), not lineItems1
• Check array format: Line items must be a JSON array of objects
• Use field IDs: In code steps, reference fields by their ID (e.g., task.fields['fBKYw']), not display name
• Verify code step output: Test the code step to ensure it returns the expected array

​

Workflow Not Triggering

• Check Trigger Conditions: Verify your trigger conditions match the expected events
• Review Workflow Logs: Check Softr’s workflow logs for errors
• Test Manually: Use Softr’s Testing tab to run the workflow with sample data

​

Tips & Best Practices

• Use Descriptive Placeholder Names: In your Google Doc template, name placeholders clearly (e.g., Project_Name instead of name) to make JSON mapping easier
• Test Each Step: Use Softr’s Testing tab to test each workflow step individually before running the full workflow
• Test with Preview Mode: Enable preview mode in DocsAutomator to test without using document credits
• Organize Your Automations: Name automations descriptively so they’re easy to identify in the Automation ID dropdown
• Store Document URLs: Add an Update record step after Create document to save the PDF URL back to your records
• Use Code Steps for Complex Data: When you need to transform or combine data from multiple records, use a Run custom code step before the Create document action
• Find Field IDs: Softr fields are referenced by ID (e.g., fBKYw), not display name. Find field IDs in your database settings or by testing a workflow step and inspecting the output data

​

FAQs

​

Which Softr plans include Workflows?

​

Can I trigger multiple document generations in one workflow?

​

Can I send the document via email?

​

Can I use the generated document URL in subsequent workflow steps?

1. Add an Update record action after the Create document step
2. Select the record to update (usually the trigger record)
3. Map the document URL from the Create document step to a File field in your record

​

E-Signatures and PDF Templates

​

Resources

• Softr Workflows Documentation
• DocsAutomator API Documentation
• Line Items Documentation
• Template Placeholders Guide