Skip to main content

Send files to a destination

Send a flow's file by email, to a web address, to an SFTP or FTPS server, to an S3 bucket, to Google Drive or Google Sheets, or as a download.

Open the destination form

Open the file's form: on the flow's We send step, select Make another file, then Create, or choose a file you already have. Under Send to, press Change, then choose New destination… in the list.

The New destination form opens under the list.

Name it and choose how it is sent

Type a Name that tells you where the file goes. Choose Send by:

  • Email. Fill in Send to (separate addresses with commas) with one or more addresses. Under More options you can add a Reply-to address, and a Subject and a Message of your own. Left blank, ProcuLink uses a default subject (the flow name and the file name). A test send puts [TEST] in front of the subject. The attachment is always named after the document, and there is no box for its name.
  • Google Drive or Google Sheets. If no Google account is connected yet, press Connect a Google account. Then press Choose folder or Choose spreadsheet. For Google Sheets use a CSV file with a header row: each send adds its rows to the end of the sheet, on the first tab unless you fill in Tab (optional).

The kinds below are grouped under A server or another system:

  • SFTP or FTPS. Fill in the Server and the Folder on the server. The Port is under More options, already set to 22 for SFTP and 21 for FTPS. SFTP can sign in with a password or a private key.
  • S3 bucket. Fill in the Bucket and the Folder. It signs in with an Access key ID and a Secret access key. The Region, and for a service other than Amazon S3 the Endpoint URL, are under More options.
  • Web address (API). Fill in the Web address (it must start with https://). The Request method, POST or PUT, is under More options.

The form shows the boxes for the way you chose.

Add the sign-in and save

Fill in the sign-in the place asks for. What each kind accepts is in Destination sign-in, keys and signing. Email needs none. Select Save and send a test (on We send) or Save: the form closes and the destination is chosen in Send to.

The destination exists. Its login is encrypted and never shown again.

If this fails

The message says why. A web address must start with https:// and must not have a user name and password written into it. A login must be filled in completely or not at all.

Use it in a file and test it

Back in the file's form, the new destination is already chosen in Send to, and the file keeps it: there is nothing more to press there. To check it with a real document, select Send a test. Once the setup is saved, new sends use the destination after you select Use these changes at the bottom of the flow; before the first save, they use it straight away. See Use changes and restore earlier versions.

You can test a destination at any time under Settings, then Destinations. A test is also sent when you press Save and send a test while you set up a new flow, and offered when you make a file from documentation. The new-flow test sends a small file marked TEST_ that holds no document data. A Google Sheets test adds no rows: it checks that we can open the spreadsheet and the tab you chose. The documentation test sends the file made from a real document in the flow, so it holds that document's values. See Destinations.

The file is tied to the destination.

Send a document and watch it

Open a document that is ready and select Send and open next. The next document that needs you opens. To watch the one you sent, open it again from Documents: under What we'll send, Deliveries lists each file with its state and number of attempts. A failed delivery shows Will retry and the reason, and ends as Couldn't deliver if it keeps failing. How retries work is in Destinations.

Every delivery is Delivered and the document is Sent.

If this fails

Read the message beside the delivery, fix the cause, then press Send and open next on the document again. Deliveries that already worked are not sent twice. See Troubleshooting.