Actions74
- ai Actions
- array Actions
- audiovideo Actions
- carbone Actions
- charts Actions
- code Actions
- data Actions
- datetime Actions
- events Actions
- files Actions
- geo Actions
- hellospaces Actions
- images Actions
- Get Metadata of an Image
- Scale an Image
- Overlay an Image on another Image
- Scale an Image to Fit Given Dimensions
- Resize an Image
- Mask an Image with Another Image
- Mask an Image with a Circle Mask
- Crops an image by the given x, y, width and height paramters.
- Convert Texts to an Image
- Convert HTML String or URL to an Image
- Generates a QRCode with given text and color.
- Get EXIF from Image
- Remove EXIF from Image
- Modify Image EXIF
- playground Actions
- spreadsheet Actions
- stripe Actions
- youtube Actions
events → Update a Pretix Ticket by id
AI-generatedOverview
This node updates a Pretix ticket by its ID within the "events" resource. It allows you to modify attendee information for a specific ticket in a given event and organizer context on the Pretix platform. This is useful for automating attendee data corrections, updating contact details, or managing ticket holder information programmatically.
Common scenarios:
- Correcting attendee names or emails after purchase.
- Updating company or address information for attendees.
- Integrating with CRM systems to keep ticket data synchronized.
Example:
Automatically update an attendee's email address if it changes in your user database.
Properties
| Name | Meaning |
|---|---|
| Organizer | The slug field of the organizer whose event/ticket you want to modify. Required. |
| Event | The slug field of the event containing the ticket to update. Required. |
| Ticket code | The unique code identifying the ticket to update. Required. |
| API Token | Your Pretix API token for authentication. Required. |
| Attendee Data Input Mode | Choose how to provide attendee data: - Expression - Manual |
| Attendee Data (Expression) | JSON object specifying fields to update for the attendee. Only provided fields will be updated. Required if using "Expression" mode. |
| Attendee Data (Manual) | Collection of fields to update for the attendee. Only provided fields will be updated. Required if using "Manual" mode. Options include: - Name - Company - Street - ZIP - City - Country - State |
Output
- json:
- On success: Contains the updated attendee/ticket data as returned by the Pretix API.
- On error: Contains an
errorfield with the error message or details.
Example output (success):
{
"json": {
"id": 123,
"code": "ABCDEF",
"attendee_name": "Jane Doe",
"attendee_email": "jane@example.com",
...
}
}
Example output (error):
{
"json": {
"error": "Invalid ticket code"
}
}
Dependencies
- Pretix API: Requires a valid API token for authentication.
- n8n Credentials: You must configure the "1001fxApi" credential in n8n with your Pretix API token.
Troubleshooting
Common issues:
- Invalid API Token: If the API token is missing or incorrect, you'll receive an authentication error. Double-check your credentials.
- Ticket Not Found: If the ticket code does not exist, the output will contain an error message such as
"Invalid ticket code". - Missing Required Fields: If required properties (Organizer, Event, Ticket code, Attendee Data) are not provided, the node will throw an error.
- Incorrect Attendee Data Format: Ensure that the attendee data matches the expected structure, especially when using "Expression" mode.
Error messages and resolutions:
"Invalid ticket code": Verify the ticket code exists for the specified event and organizer."Authentication failed": Check your API token and permissions."Missing required property": Make sure all required fields are filled in the node configuration.