Connectors
Connectors move tickets between Fesk and other systems. A source connector pulls work in from somewhere else; a destination connector pushes Fesk events out. Transformation rules reshape the data in between so each side sees fields it understands.
Connectors live under Settings → Connectors and require an admin role.
Source connectors
A source connector brings tickets into Fesk from an external system on a schedule or via incoming events. Use them to consolidate work that originates elsewhere into one board.
For each source connector you can:
- Configure the connection and what to pull
- Test the connection before enabling it
- Toggle it on or off without deleting the configuration
Destination connectors
A destination connector sends Fesk events out to another system, to mirror tickets into a downstream tool, feed a data pipeline, or notify another platform. Like source connectors, they support a Test action and an on/off toggle.
If all you need is to notify an HTTPS endpoint when something happens, a lighter-weight webhook may be the better fit. Destination connectors are for richer, system-to-system delivery.
Transformation rules
Different systems name and shape fields differently. Transformation rules (under Settings → Connectors → Transformation Rules) map and modify fields as data passes through a connector, renaming fields, setting defaults, or converting values so both sides line up.
Each rule can be tested against sample data to confirm the output before you rely on it, and toggled on or off.
A typical setup
- Create a source connector to pull tickets in.
- Add a transformation rule to map the external fields onto Fesk's ticket types and fields.
- Optionally add a destination connector to push updates back out.
- Test each piece, then enable them.
Related
- For simple event notifications to a URL, use webhooks.
- To turn incoming email into tickets instead, see email integration.