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 → Resend Pretix Ticket Link
AI-generatedOverview
The "Resend Pretix Ticket Link" operation under the "events" resource is designed to trigger a resend of the ticket link email for a specific order in a Pretix event. This is useful when attendees have lost their original ticket email or need the ticket link sent again. Common scenarios include customer support workflows, automated reminders, or bulk re-sending of tickets after updates.
Practical Example:
If an attendee contacts your support team because they did not receive their ticket, you can use this node to automatically resend the ticket link by providing the relevant organizer, event, and order code.
Properties
| Name | Meaning |
|---|---|
| Organizer | The slug field of the organizer to modify. (Required) |
| Event | The slug field of the event to modify. (Required) |
| Code | The code field of the order to send an email for. (Required) |
| API Token | Your pretix API Token. Used for authenticating requests to the Pretix API. (Required) |
Output
- The output will be a JSON object containing the response from the Pretix API after attempting to resend the ticket link.
- If successful, the response typically includes confirmation details or status information.
- If there is an error, the output will contain an
errorfield with the error message or details.
Example Output:
{
"status": "success",
"message": "Ticket link resent successfully."
}
or, in case of error:
{
"error": "Order code not found."
}
Dependencies
- Pretix API: Requires access to the Pretix API endpoint.
- API Token: You must provide a valid Pretix API token with permissions to manage orders and send emails.
- n8n Credentials: The node expects credentials named
1001fxApito be configured in n8n.
Troubleshooting
- Invalid API Token: If the API token is missing or incorrect, you may receive authentication errors such as
"Invalid API key"or"Unauthorized". Ensure the token is correct and has sufficient permissions. - Incorrect Organizer/Event/Code: If any of these fields are incorrect, you might see errors like
"Organizer not found","Event not found", or"Order code not found."Double-check the slugs and codes provided. - Network Issues: Errors related to network connectivity or timeouts may occur if the Pretix API is unreachable.
- Error Handling: If an error occurs and "Continue On Fail" is enabled, the output will include an
errorfield instead of stopping the workflow.