HTTP, FTP, Email, S3 Data Deliveries

Set up a scheduled file export of Invoca data to an HTTP endpoint, FTP folder, email address, or Amazon S3 bucket, when an API-based integration isn’t possible.

​

Requesting a new data delivery

• File name — a custom name, useful if the receiving system requires a specific naming convention
• File format — CSV, tab-, or pipe-delimited. For PGP encryption (disabled by default), send your public key as a key file or ASCII-armored text — Invoca can’t decrypt the file once encrypted, so keep your private key secure. Encrypted files are delivered as .csv.gpg
• Report type and data — built from the Calls or Transactions report, with further customization available (see FAQ below); review those reports directly in Invoca if you’re unsure what data is available
• Schedule — daily, weekly, or monthly, with your chosen day, hour, and time zone; each delivery includes all data since the previous one
• Destination, with the corresponding details:
  • HTTP — delivery endpoint, optional headers, whether to use today’s or yesterday’s date for any date substitutions, and credentials for delivery
  • FTP or SFTP — host, port, username and password (or an SSH private key, optionally with a passphrase), and path/directory if applicable
  • Email — recipient address(es) and subject line (delivered as an attachment)
  • Amazon S3 — AWS Access Key ID, AWS Secret Access Key, and the bucket name

​

Limitations

• FTPS and HTTPS aren’t supported (plain HTTP is)
• FTP and SFTP deliveries can only use ports 21 and 22
• Files can’t be compressed (no .zip, .gzip, .tar)
• Formula-derived values aren’t supported — for example, a count of how many Signals were met on a call
• Invoca only delivers to an FTP or S3 destination you host; it doesn’t support a third party pulling files directly from an Invoca-hosted location
• Very large files can’t be split across multiple deliveries

​

Customizing your data delivery

• Custom headers — rename any column from its default report field name to match a receiving system’s requirements
• Row filtering — filter on a specific value, multiple values, or simply whether a value is present at all (useful when a receiving system requires an identifier to process a row); filters can be combined
• Hard-coded values — populate a column with a fixed value not present in Invoca reports (for example, always passing “1” in a Count column), or translate an existing value into another form (for example, mapping utm_source=ppc to “Paid Search”)

​

FAQ

​

Where to go next

• Can SFTP Files Be Resent?
• Multiple Days of Data in Daily Delivery Files