Invoiced Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to an Invoiced location.

Invoiced

1. Click the + icon on the Nexset that will be sent to the Invoiced destination, and select the Send to Destination option from the menu.

2. Select the Invoiced connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Invoiced account, and click Next; or, create a new Invoiced credential for use in this flow.

3. In Nexla, Invoiced destinations can be created using pre-built endpoint templates, which expedite destination setup for common Invoiced write operations. Each template is designed specifically for the corresponding Invoiced endpoint, making destination setup easy and efficient.
   • To configure this destination using a template, follow the instructions in Configure Using a Template.

   Invoiced destinations can also be configured manually, allowing you to send data to any valid Invoiced REST API endpoint — including creating invoices, customers, payments, subscriptions, and other billing records.
   • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Invoiced endpoints. Each template is designed specifically for the corresponding Invoiced endpoint, making destination setup easy and efficient.

Endpoint Settings

• Select the endpoint to which this destination will send data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your destination for this endpoint.

  Create Customer

  Creates a new customer record in Invoiced. Use this endpoint to write customer account data from any Nexset into Invoiced to automate customer onboarding or CRM-to-billing synchronization.

  • Issues a POST request to https://api.invoiced.com/customers. The request body is a JSON object containing customer fields such as name, email, address, and payment terms.
  • After a successful create, Invoiced returns the full customer record including the system-assigned numeric ID. Use the Response Webhook option to capture this ID in a downstream Nexset.

  Ensure that the field names in your Nexset match the Invoiced API customer field names. Use the Exclude Attributes option to omit any Nexset fields not accepted by this endpoint to prevent API errors.

  Attach Payment Method to Customer

  Attaches a payment method (card or bank account) to an existing customer in Invoiced. Use this endpoint to automate payment method setup as part of a customer onboarding workflow.

  • Issues a POST request to the customer payment sources endpoint. The Customer Id parameter must be configured with the numeric ID of the customer to which the payment method will be attached.
  • The request body contains payment method details. Use the Response Webhook to capture the newly created payment source ID.

  Handle payment method data carefully and ensure your integration complies with PCI DSS requirements. Only tokenized payment data should flow through Nexla — do not pass raw card numbers.

  Create Invoice

  Creates a new invoice in Invoiced. Use this endpoint to generate invoices from billing data flowing through Nexla, enabling automated invoice generation from external systems.

  • Issues a POST request to https://api.invoiced.com/invoices. The request body accepts customer ID, line items, due date, notes, and other invoice fields.
  • Invoiced returns the full invoice record including the system-assigned ID after a successful create. Use the Response Webhook to capture the invoice ID downstream.

  A customer must exist in Invoiced before an invoice can be created. Chain a Create Customer destination with a Create Invoice destination using the Response Webhook to capture the customer ID needed for invoice creation.

  Record Payment

  Records a new payment against an invoice or customer balance in Invoiced. Use this endpoint to synchronize payment records from external payment processors or banking data into Invoiced.

  • Issues a POST request to https://api.invoiced.com/payments. The request body accepts customer ID or invoice ID, payment amount, payment method, and date.
  • Invoiced returns the full payment record including the system-assigned ID after a successful create. Use the Response Webhook to capture payment IDs downstream.

  Payments can be applied to specific invoices or to a customer's general balance. Ensure the invoice or customer ID in your Nexset matches an existing record in Invoiced before sending to avoid application errors.

  Create Subscription

  Creates a new subscription for recurring billing in Invoiced. Use this endpoint to automate subscription setup when customers are enrolled in recurring billing plans via external systems.

  • Issues a POST request to the subscriptions endpoint. The request body accepts customer ID, plan ID, start date, and optional quantity and discount fields.
  • Invoiced returns the full subscription record including the system-assigned ID after a successful create.

  Both the customer and the plan must exist in Invoiced before a subscription can be created. Use the List Plans source endpoint to retrieve plan IDs, and ensure the customer record is available in Invoiced before activating this destination.

  Update Customer

  Updates an existing customer's details in Invoiced, such as address, payment terms, or autopay settings. Use this endpoint to keep customer records in Invoiced synchronized with an external CRM or ERP system.

  • Issues a PATCH request to https://api.invoiced.com/customers/{'{id}'}. The Id parameter must be configured with the numeric Invoiced customer ID to update.
  • Only the fields included in the request body are updated — existing fields not included in the payload are preserved.

  Use PATCH rather than PUT for customer updates to avoid overwriting fields not present in your Nexset. Ensure the customer ID in your Nexset corresponds to an existing Invoiced customer record.

  Update Invoice

  Updates an existing invoice's line items, due date, status, or other details in Invoiced. Use this endpoint to synchronize invoice changes from an external system back into Invoiced.

  • Issues a PATCH request to https://api.invoiced.com/invoices/{'{id}'}. The Id parameter must be configured with the numeric Invoiced invoice ID to update.
  • Only the fields included in the request body are updated. Invoiced validates the submitted data before applying changes.

  Invoices in certain statuses (e.g., paid or voided) may be locked and not editable. Verify invoice status in your Nexset before sending updates to avoid errors on locked records.

  Issue Credit Note

  Issues a credit note against a customer or invoice in Invoiced. Use this endpoint to automate the creation of credit notes for refunds, adjustments, or billing corrections from a Nexla data flow.

  • Issues a POST request to the credit notes endpoint. The request body accepts the customer ID, associated invoice, amount, and line item details.
  • Invoiced returns the full credit note record including the system-assigned ID after a successful create.

  Credit notes reduce the balance owed by a customer. Ensure that the associated customer or invoice ID in your Nexset exists in Invoiced before activating this destination.

  Add Contact to Customer

  Adds a new contact person to an existing customer account in Invoiced. Use this endpoint to synchronize billing contact data from a CRM or HR system into Invoiced.

  • Issues a POST request to the customer contacts endpoint. The Customer Id parameter must be configured with the numeric ID of the customer to which the contact will be added.
  • The request body accepts contact name, email, phone, and role fields. Invoiced returns the created contact record after a successful call.

  Contacts are the individual people associated with a customer account for billing and communication purposes. Use the Response Webhook to capture the newly created contact ID for downstream reference.

  Create Estimate

  Creates a new estimate or quote for a customer in Invoiced. Use this endpoint to generate quotes from pricing or CPQ data flowing through Nexla.

  • Issues a POST request to the estimates endpoint. The request body accepts customer ID, line items, expiration date, and notes.
  • Invoiced returns the full estimate record including the system-assigned ID after a successful create. Estimates can later be converted to invoices.

  Estimates require a valid customer to already exist in Invoiced. Use the Response Webhook to capture the estimate ID, which can be referenced when converting the estimate to an invoice.

  Create Task

  Creates a follow-up task in Invoiced for collections, onboarding, or other customer-related actions. Use this endpoint to automatically generate tasks from workflow data flowing through Nexla.

  • Issues a POST request to the tasks endpoint. The request body accepts task name, due date, assignee, and the associated customer or invoice ID.
  • Invoiced returns the created task record after a successful call. Use the Response Webhook to capture the task ID downstream.

  Tasks can be linked to specific customers or invoices for context. Use this endpoint in collections automation flows to create follow-up tasks whenever a payment becomes overdue.

  Delete Invoice

  Voids or deletes a draft or issued invoice in Invoiced. Use this endpoint to automate invoice cancellation or voiding from a data flow processing cancellation or correction events.

  • Issues a DELETE request to https://api.invoiced.com/invoices/{'{id}'}. The Id parameter must be configured with the numeric ID of the invoice to delete or void.
  • Only draft invoices can be permanently deleted; issued invoices are voided rather than deleted.

  Invoice deletion and voiding are permanent operations. Verify that the correct invoice IDs are flowing through your Nexset before activating this destination, and consider testing with a single record before processing in bulk.

Endpoint Testing

Once the selected endpoint template has been configured, Nexla can send a test payload to the Invoiced API to ensure that the destination is configured correctly.

1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Invoiced API using the current settings.

Configure Manually

Invoiced destinations can be manually configured to send data to any valid Invoiced REST API endpoint. This allows you to create invoices, customers, payments, subscriptions, and other billing records in Invoiced from data flowing through Nexla. You can also configure Nexla to automatically send the response received from the Invoiced API after each call to a new Nexla webhook data source.

First, select the API method that will be used for calls to the Invoiced API from the Method pulldown menu. Common methods for Invoiced destination operations include:

• POST: For creating new resources (e.g., creating a new invoice, customer, or payment)
• PATCH: For updating existing resources (e.g., updating invoice details or customer information)
• PUT: For replacing existing resources entirely
• DELETE: For removing resources (e.g., voiding a draft invoice)

Data Format

4. Select the format in which the Nexset data will be sent to the Invoiced API from the Content Format pulldown menu. The Invoiced API accepts and returns data in JSON format. Select JSON to ensure Nexla sends data in the format expected by Invoiced.

   The Invoiced API expects JSON-formatted request bodies for all write operations (POST, PATCH, PUT). Ensure that the field names in your Nexset match the Invoiced API's expected parameter names for the target resource. For complete field reference, see the Invoiced API Documentation.

API Endpoint URL

5. Enter the URL of the Invoiced API endpoint to which you want to send the Nexset data in the URL field.

   Common Invoiced destination endpoint patterns include:

   • Create a new invoice: https://api.invoiced.com/invoices (POST)
   • Update an invoice: https://api.invoiced.com/invoices/{'{id}'} (PATCH)
   • Create a new customer: https://api.invoiced.com/customers (POST)
   • Update a customer: https://api.invoiced.com/customers/{'{id}'} (PATCH)
   • Create a payment: https://api.invoiced.com/payments (POST)
   • Create a subscription: https://api.invoiced.com/subscriptions (POST)
   • Create a credit note: https://api.invoiced.com/credit_notes (POST)

   For update operations (PATCH or PUT), include the numeric ID of the record to be updated at the end of the URL. For example, to update invoice with ID 2048: https://api.invoiced.com/invoices/2048.

   When creating resources through the API, Invoiced validates the submitted data and returns the created resource—including the system-assigned ID—in the response. You can capture this response using the Response Webhook option described below to track created record IDs in a downstream Nexset.

Request Headers

Optional

• If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

  You do not need to include the Authorization header or authentication details in the request headers—these are handled automatically by Nexla based on your Invoiced credential configuration.

Exclude Attributes from the Call

Optional

• If any record attributes in the Nexset should be omitted when sending data to this Invoiced destination, select the attributes from the Exclude Attributes pulldown menu.

• Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

  Excluding attributes is useful when your Nexset contains fields that are not valid parameters for the Invoiced API endpoint you are targeting. Sending unknown fields to the Invoiced API may result in errors or unexpected behavior, so use this option to filter out any fields not recognized by the target endpoint.

Record Batching

Optional

1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

   Invoiced's API processes individual records for most create/update operations. Evaluate whether the specific Invoiced endpoint you are targeting supports batch payloads before enabling record batching. For endpoints that accept only a single object per request, send records individually without batching enabled.

Response Webhook

Optional

Nexla can automatically send the response received from the Invoiced API after each call to a new Nexla webhook data source. This option allows you to track the status of each API call and capture important information returned by Invoiced—such as the system-assigned ID of a newly created invoice or customer.

• To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload

Sample request payloads containing a portion of the Nexset data that will be sent to the Invoiced API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

• Click on a sample request payload to expand it and view the complete payload content.

• Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing

After all endpoint settings have been configured, Nexla can send a test payload to the Invoiced API to ensure that the destination is configured correctly.

1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Invoiced API using the current settings.

Save & Activate the Destination

• Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Invoiced endpoint, open the destination resource menu, and select Activate.

  The Nexset data will not be sent to Invoiced until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.