Skip to main content

Create ConnectWise Attachments

Use Create ConnectWise Attachments to upload email files, form uploads, or files produced by earlier action steps to an existing ConnectWise record. The action uploads each selected file separately, so a failed upload can retry without uploading successful files again.

Parameters​

ConnectWise Connection​

Select the ConnectWise connection to use. Leave this field empty to use the default ConnectWise connection.

Record Type​

Select the type of record that will receive the files. Supported common record types include tickets, companies, contacts, configurations, opportunities, projects, agreements, sales orders, purchase orders, expenses, activities, invoices, and time entries.

Record ID​

Enter the positive numeric ID of the ConnectWise record. This field supports text expressions, such as an ID returned by an earlier action step.

Files​

Select files from available email data, form uploads, or previous action results. By default, the action selects inbound email attachments and inline images.

Select All Files to include every available file. In an email workflow, this can create and include the original email as an EML file and the rendered email image when those file sources are available.

You can filter selected files by filename, content type, or maximum size.

Private​

Enable this option to mark each uploaded document as private in ConnectWise.

Error Handling​

Choose what the workflow should do when ConnectWise rejects an upload or the request fails. The action applies this setting to each file independently.

Returned Variables​

If you configure Store the results in Variable, the action returns:

VariableTypeDescription
attached_countnumberNumber of files successfully attached.
filenamesarrayFilenames successfully attached.
documentsarrayDocument details returned by ConnectWise for successful uploads.

Each document can include its ConnectWise document ID, title, filename, owner, size, GUID, and visibility flags.

Notes​

  • ConnectWise applies its own file size, record permission, and document restrictions.
  • The selected files must belong to the current workflow run and customer account.
  • The action does not check for existing attachments with matching filenames or content.