Fieldcode Manual

Tip: You can use filters for better results

Expert topic

Outgoing Mapping configuration doesn't require a developer to be involved - however - self-configuration is only suggested for power users of our applications.

Inside the Admin panel go to Settings → Outgoing Mappings to open the table view of outgoing mappings. From there on you have multiple variants of establishing interaction with another system. You can either do it with the help of the setup wizard inside the page itself, which guides you through step-by-step or manage systemspermissions, and security configurations manually one after another.

Outgoing mappings define how data is sent from Fieldcode to external systems. They allow you to control which ticket information is shared, in what format, and under which conditions.

Unlike incoming mappings, outgoing mappings are easier to configure and require fewer transformation rules.

Use outgoing mappings when you want to:

  • Send ticket updates to an external system (e.g., a partner’s platform)
  • Notify external systems about status changes, technician assignments, or results
  • Automate data exchange without manual exports
How outgoing mappings work:
  • Trigger: An event in Fieldcode (e.g., ticket status change) triggers the mapping.
  • Mapping: The system uses the defined mapping to format the data.
  • Delivery: The data is sent to the configured endpoint (e.g., via API or webhook).
Example use case:

You want to notify a partner system every time a ticket is completed. You could create an outgoing mapping that:
  • Triggers on the “Ticket completed” event
  • Sends the ticket ID, status, and result
  • Delivers the data to the partner’s API endpoint
  1. The Active toggle is enabled by default. Enables or disables the mapping.
  2. Enter a name. The name field is unique identifier for the mapping.
Click on image to expand/minimize
  1. (Optional) - Add a description for your outgoing mapping.
Click on image to expand/minimize
  1. Select a system from the dropdown. The system you select here is the external system to receive the data.
Click on image to expand/minimize
  1. Select a object from the dropdown. The object field defines the type of data object that will be sent to the external system — for example ticket data or a custom object of your choice.
  2. Click on the Continue button.
Click on image to expand/minimize

You can create a outgoing mapping by using Fieldcode Python. Please check out the related topics at the end of this topic. Click Save after adding your code, in order to be able to test your outgoing mapping.

Click on image to expand/minimize

You can test your outgoing mappings after clicking save after adding your code. You can test your outgoing mappings with existing tickets or existing records. If you don’t have existing records you will not be able to test:

Example of testing a mapping (Figurative example)
Was this topic helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we further improve this topic?
Please provide the reason for your vote. This will help us improve this topic.
Navigation