|

Docs

General
↳ See all 22 articles
Core Features
Apps & Integrations Setup
↳ See all 345 articles
Tips & Tricks
Accounts & Billing
Workflows
App Builder
↳ See all 12 articles
/ Documentation /Core Features/ Using the Convert to File App in OttoKit

Using the Convert to File App in OttoKit

Need to turn workflow data into downloadable files on the fly, HTML, CSV, ICS calendars, spreadsheets, PDFs, or even Base64? The Convert to File App lets you generate clean, ready-to-use files directly inside your automations. No external converters, no manual formatting, and no temporary scripts required.

You can pass raw data, mapped fields, or structured content depending on the file type you’re generating. The app outputs a public file URL you can use anywhere in your workflow.

Note: This integration creates files only. It does not interpret or execute code inside the file (HTML, JS, etc.).

Actions in the Convert to File App

1) Convert to HTML

This action allows you to turn raw HTML content into a downloadable .html file.

To convert to HTML:

  1. Add a new action to your workflow.
  2. Search for Convert to File and select it.
  3. Choose Convert to HTML.
  4. Click Continue to open the Configure tab.
  5. Fill in the fields:

Data (required) – Specify or map the HTML data.
This should include your full HTML boilerplate, such as:

<!DOCTYPE html>

<html>

<head><meta charset=”UTF-8″><title>Sample</title></head>

<body><h1>Hello World</h1></body>

</html>

Click Show Optional Fields for additional configuration:

Filename – Specify the filename, e.g., index.html or index.
Inline CSS – Choose whether to inline CSS automatically (True or False).
Header Rows – Select whether to include header rows when converting table data (True or False).

  1. Click Continue to open the Test Step tab.
  2. Click Test to generate your HTML file.
  3. If everything looks good, click Save.
Annotation On 2025 11 27 At 15 18 02 1024x490

2) Convert to CSV

Turns structured CSV text into a .csv file ready for download or further processing.

To convert to CSV:

  1. Add a new action.
  2. Search for Convert to File.
  3. Select Convert to CSV.
  4. Click Continue.
  5. Fill in the fields:

Data (required) – Specify or map the CSV data (raw text).

Click Show Optional Fields for additional configuration:

Filename – The file’s name, e.g., index.csv or index.
Delimiter – Specify the CSV delimiter, e.g., , or ;.
Header Rows – Add header rows or not (True or False).

  1. Click Test, then Save.
Screenshot 2025 11 27 152956 1024x488

3) Convert to ICS

Create calendar events in .ics format from workflow data.

To convert to ICS:

  1. Add a new action.
  2. Search for Convert to File and choose Convert to ICS.
  3. Click Continue.
  4. Fill in the fields:

Data – Provide ICS markup or add a space ” ” when using the form fields below.
Click “Add attendees” to include one or more attendees.

Then specify:

  • Filename – e.g., event.ics or index.
  • Event Title – Name of the event.
  • Start Time – YYYY-MM-DDTHH:MM:SSZ.
  • End Time – Same format as above.
  • All Day – True/False.
  • Location – Event location.
  • Description – Event details.
  • Organizer Email Address
  • Organizer Name
  • Calendar Name
  • Timezone – e.g., “America/New_York”.
  • Status – Confirmed, cancelled, or tentative.
  1. Test and save.
Image 1 1024x488

A link to the ICS is then generated:

Image 5 1024x490

4) Convert to JSON

This action allows you to generate a .json file from your mapped data.

To convert to JSON:

  1. Add a new action and select Convert to JSON.
  2. Configure the fields:

Data (required) – Wrap your data in a top-level key:

{

  “data”: {

    “name”: “OttoKit”,

    “version”: 1

  }

}

Filename – e.g., index.json.
Pretty – Enable pretty formatting (True/False).

  1. Test and save.
Image 3 1024x445

5) Convert to ODS

Convert mapped data into an OpenDocument Spreadsheet (.ods).

To convert to ODS:

  1. Add a new action and choose Convert to ODS.
  2. Configure the fields:

Data (required) – Specify the ODS-compatible data.

Show Optional Fields:

  • Filename – e.g., index.ods.
  • Sheet Name – Name of the spreadsheet tab.
  • Header Rows – Include header rows or not.
  • Compression – Compress file output (True/False).
  1. Test and save.
Image 9 1024x486

A link to the ICS is then generated:

Screenshot 2025 12 01 075227 1024x488

6) Convert to RTF

Generate a Rich Text Format file from raw RTF markup.

To convert to RTF:

  1. Add the action and select Convert to RTF.
  2. Configure:

Data (required) – Specify or map the RTF content.

Show Optional Fields:

  • Filename – e.g., index.rtf.
  • Line Separator – e.g., \n.
  • Header Rows – Include header rows (True/False).
  1. Test and save.
Image 8 1024x490

7) Convert to TXT

This action allows you to create a plain text file with flexible formatting options.

To convert to TXT:

  1. Add the action and choose Convert to TXT.
  2. Configure:

Data (required) – Specify or map the text content.

Show Optional Fields:

  • Filename – e.g., index.txt.
  • Encoding – e.g., “utf-8”.
  • Line Separator – e.g., \n.
  • Pretty – Enable pretty formatting (True/False).
  • Max Width Per Line – Outline the maximum characters per line.
  • Indent – Indent string for formatting.
  • Trim – Trim whitespace (True/False).
  1. Test and save.
Image 10 1024x489

8) Convert to XLSX

Convert workflow data into an Excel .xlsx file.

To convert to XLSX:

  1. Add a new action and select Convert to XLSX.
  2. Configure:

Data (required) – Map XLSX-compatible data.

Show Optional Fields:

  • Filename – e.g., index.xlsx.
  • Sheet Name – Tab name.
  • Header Rows – Include headers (True/False).
  • Compression – Compress output (True/False).
  1. Test and save.

9) Convert to PDF

Turn mapped content into a downloadable PDF file.

To convert to PDF:

  1. Add the action and choose Convert to PDF.
  2. Configure:

Data (required) – Specify or map the PDF data.

Show Optional Fields:

  • Filename – e.g., index.pdf.
  • Page Size – e.g., A4.
  • Font Size – e.g., 18.
  • Margin – Page margins.
  • Layout – Landscape or Portrait.
  • Header Row – Include header rows or not.
  1. Test and save.
Screenshot 2025 12 01 080414 1024x485

10) Move Base64 String to File

Convert Base64-encoded data into a downloadable file.

To move Base64 to a File:

  1. Add the action and select Move Base64 String to File.
  2. Under the configure tab:

Data (required) – Map the Base64 string.
Mime Type – Choose the target MIME type (pdf, jpeg, html, csv, etc).

Optional Fields:

  • Filename – File name.
  • Encoding – utf8, ascii, or binary.
  1. Test and save.
Image 4 1024x486

11) Convert to Base64

Convert a file URL into a standard Base64 format.

To convert:

  1. Add the action and choose Convert to Base64.
  2. Configure:

URL (required) – Map the file URL.
Filename – Optional output filename.

  1. Test and save.
Image 7 1024x489

Here is the Base64 file:

Annotation On 2025 12 01 At 08 16 07 1024x488

12) Convert to Raw Base64

Generate raw Base64 output without formatting.

To convert:

  1. Add the action and choose Convert to Raw Base64.
  2. Configure:

URL (required) – Map the file URL.

  1. Test and save.

13) Fetch File via Pre-Signed URL

Download a file from a pre-signed URL and return a public URL for the uploaded file.

To fetch:

  1. Add the action and select Fetch File via Pre-Signed URL.
  2. Configure:

URL (required) – Enter the pre-signed URL.
Filename – Provide the output filename.

  1. Test and save.

Practical Use Cases

Below are three practical examples showing how to put it to work.

Practical Example 1: Generate a PDF Invoice After a SureCart Order

Scenario: You run an online store using SureCart. Each time a customer places an order, you want to automatically generate a PDF invoice and email it to them. With the Convert to File app, you can create the PDF from the order details and pass the file link to an email step, all without any manual work.

Step 1: Set Up the Trigger

  1. Create a new workflow in OttoKit.
  2. Click the trigger area and search for SureCart.
  3. Select Order Created as the trigger event.
  4. Connect your SureCart account.
  5. Click Save Trigger.
  6. Click Fetch Data to load a sample order. This loads fields like customer name, email, and order total that you will use in the next steps.

Step 2: Add the Convert to File App

  1. Click the + button below the trigger step.
  2. Search for Convert to File and select it.
  3. Choose Convert to PDF as the action.
  4. Click Continue to open the Configure tab.
  5. Data (required) — Type the content you want in the PDF. Use @ to map fields from the trigger. For example: Order: #[Order Number], Customer: [Customer Name], Total: [Order Total].
  6. Click Show Optional Fields and set the following:
FieldWhat to Enter
Filenameinvoice.pdf
Page SizeA4
LayoutPortrait
  1. Click Continue, then click Test to generate the PDF.
  2. Once the test passes, you will see a public URL for your PDF file in the output. Click Save.

Step 3: Email the Invoice to the Customer

  1. Click the + button below the Convert to File step.
  2. Search for Gmail (or your preferred email app) and select Send Email.
  3. To: map the customer email from the SureCart trigger.
  4. Subject: Your Invoice for Order #[map Order Number].
  5. Body: type your message and use @ to map the File URL from the Convert to File step. Include it as a download link for the invoice.
  6. Click Test, then Save.
  7. Click Publish Workflow in the top-right corner.

That is it. Now every new SureCart order automatically generates a PDF invoice and emails it to the customer.

Export Form Submissions to a CSV File

Scenario: You collect contact or lead information through a form on your website. Each time someone submits the form, you want to automatically create a CSV file with the submitted data and save it to Google Drive for your team. No manual exports needed.

Step 1: Set Up the Trigger

  1. Create a new workflow in OttoKit.
  2. Click the trigger area and search for your form plugin, such as SureForms, Gravity Forms, or WPForms.
  3. Select New Form Submission as the trigger event.
  4. Connect your account and select the specific form to monitor.
  5. Click Save Trigger, then Fetch Data to load a sample submission.

Step 2: Add the Convert to File App

  1. Click the + button below the trigger.
  2. Search for Convert to File and select it.
  3. Choose Convert to CSV.
  4. Click Continue.
  5. Data (required) — Enter your CSV content in comma-separated format. Type @ to map each field from your form submission. For example: Name, Email, Message on the first line, then [First Name],[Email Address],[Message] on the second line.
  6. Click Show Optional Fields and set the following:
  1. Click Continue, then click Test to generate the CSV file.
  2. You will see a public URL for the file in the test output. Click Save.
FieldWhat to Enter
Filenameform-submission.csv
Delimiter, (comma)
Header RowsTrue

Step 3: Save the CSV File to Google Drive

  1. Click the + button below the Convert to File step.
  2. Search for Google Drive and select Upload File.
  3. File URL: map the File URL output from the Convert to File step.
  4. Filename: form-submission.csv.
  5. Folder: select the Google Drive folder where submissions should be saved.
  6. Click Test, then Save.
  7. Click Publish Workflow.

That is it. Now every form submission automatically creates a CSV file and saves it to your Google Drive folder.

Send a Calendar Invite After an Appointment Booking

Scenario: You take appointment bookings through LatePoint or a similar booking plugin. When a customer books a session, you want to automatically generate a calendar invite file (.ics) and email it to them so they can add the event to their calendar with one click. The Convert to ICS action in the Convert to File app handles this automatically.

Step 1: Set Up the Trigger

  1. Create a new workflow in OttoKit.
  2. Click the trigger area and search for LatePoint (or your booking plugin).
  3. Select New Appointment as the trigger event.
  4. Connect your account.
  5. Click Save Trigger, then Fetch Data to load a sample booking. You will need the appointment date, time, service name, and customer email from this data.

Step 2: Add the Convert to File App

  1. Click the + button below the trigger.
  2. Search for Convert to File and select it.
  3. Choose Convert to ICS.
  4. Click Continue.
  5. Data — Leave this blank or enter a single space ” ” since you will be filling in the form fields below instead.
  6. Fill in the event details using @ to map fields from the trigger:
FieldWhat to Enter
Event TitleMap the service or appointment name from the trigger
Start TimeMap the appointment start time (format: YYYY-MM-DDTHH:MM:SSZ)
End TimeMap the appointment end time (same format)
LocationMap the location or type a value like Online
Descriptione.g., Your appointment with [Provider Name]
Organizer Email AddressYour business email address
Organizer NameYour business name
Timezonee.g., America/New_York
StatusConfirmed
Filename (optional)appointment.ics
  1. Click Add Attendees and map the customer email from the trigger to include them in the invite.
  2. Click Continue, then click Test to generate the .ics file.
  3. You will see a public URL for the file in the output. Click Save.

Step 3: Email the Calendar Invite to the Customer

  1. Click the + button below the Convert to File step.
  2. Search for Gmail and select Send Email.
  3. To: map the customer email from the trigger.
  4. Subject: Your Appointment is Confirmed.
  5. Body: type your message and use @ to map the File URL from the Convert to File step. Include it as a link so the customer can download the calendar file.
  6. Click Test, then Save.
  7. Click Publish Workflow.

That is it. Now, every new booking automatically sends the customer a calendar invite file they can open and save directly to their calendar.

With the Convert to File App in OttoKit, you can turn structured data into real files, spreadsheets, documents, calendars, text files, or even Base64 in seconds. No outside tools, no formatting headaches, and no manual conversions.

Whether you’re building automated reports, generating files for clients, packaging data for downstream systems, or converting workflow output into downloadable documents, OttoKit makes it fast, flexible, and reliable.

Start using the Convert to File App today and add powerful file-generation capabilities to every workflow you build.

Was this doc helpful?
What went wrong?

We don't respond to the article feedback, we use it to improve our support content.

Need help? Contact Support
%title %title
Scroll to Top