How can we help you?

1. Overview & System Requirements

The Gravity Forms Zendesk Integration Add-on connects your WordPress forms directly to Zendesk Support—the world’s leading enterprise customer service and ticketing ecosystem. By automating customer profile creation, ticket routing, automated tags, and custom ticket fields upon form submission, customer operations teams resolve inquiries substantially faster while eliminating manual copy-pasting and costly third-party webhook middleware.

Whether you deploy complex multi-page warranty claim forms, VIP enterprise technical escalations, customer onboarding questionnaires, or general helpdesk inquiries, this add-on maps each submission directly into Zendesk REST API v2 endpoints. Incoming submissions automatically create a new customer ticket or append private agent notes to existing open conversations, ensuring your support desk operates with complete context and zero latency.

2. Authentication & Zendesk API Setup

The integration communicates with Zendesk using encrypted Basic Token authentication via the official REST API v2:

Generating Your Zendesk API Token

1. Log in to your Zendesk Admin Center at yourcompany.zendesk.com/admin.
2. In the left sidebar, navigate to Apps and integrations → Zendesk API.
3. Under the Settings tab, ensure Token Access is toggled to Active.
4. Click Add API token, supply a descriptive label (such as Gravity Forms Production), and copy the generated token string to your clipboard.
5. Confirm your account administrator email address associated with the token.

Configuring in WordPress Dashboard

1. In your WordPress dashboard, navigate to Forms → Settings → Zendesk.
2. Enter your Zendesk Subdomain (the prefix before .zendesk.com).
3. Enter your Admin Email Address and paste the generated API Token.
4. Click Save Settings. The plugin connects to Zendesk to verify credentials. A green success confirmation verifies proper connection.

3. Feed Configuration & Field Mapping

Feeds allow you to configure custom ticket creation rules for each form across your WordPress site:

Core Ticket & Requester Fields

• Subject Line: Use static text or dynamic merge tags (e.g. Support Request: {Subject:2} - Order #{Order_ID:5}).
• Requester Details: Map Full Name and Work Email. The add-on looks up the user by email in Zendesk. If found, the ticket attaches to their history; if not, a new user profile is created automatically.
• Ticket Body (Comment): Map the primary textarea field or compile form inputs into a formatted HTML or Markdown message.
• Priority & Type: Set static values or map dropdowns for Priority (Low, Normal, High, Urgent) and Type (Question, Incident, Problem, Task).
• Custom Ticket Fields: Map custom fields (e.g., License Key, Software Version, Operating System) directly into Zendesk custom ticket fields using their numerical Field IDs.
• Automated Tags: Attach static tags (e.g. web_lead, vip_account) or pass comma-separated tags dynamically from checkboxes.

Conditional Routing & Group Assignment

Leverage Gravity Forms conditional logic to route support inquiries dynamically:

• VIP Support Routing: Route enterprise accounts with annual contracts directly to your dedicated VIP Support Group with Urgent priority.
• Departmental Triage: Route billing inquiries to the Finance Support Group feed while directing technical error inquiries to Tier 2 Engineering.
• Spam Filtering: Suppress ticket creation for submissions flagged as unsolicited vendor pitches.

4. Advanced Customer Operations Workflows

Connecting Gravity Forms with Zendesk supports sophisticated enterprise support architectures:

• Automated Private Internal Notes: Submitters can generate a ticket with an initial public requester comment, while internal audit fields (such as client IP, user agent, referral source, and order total) are appended as a private internal agent note.
• File Attachment Synchronization: When customers upload screenshots, PDF error traces, or diagnostic logs through the form, secure download links are embedded directly into the ticket description so agents can inspect them immediately.
• Zendesk Macro & SLA Triggers: Injected tags immediately activate Zendesk business rules, sending immediate automated auto-replies, calculating SLA response clocks, and assigning tickets to the next available agent round-robin.
• Multi-Brand Routing: For companies running multiple brand storefronts on a single WordPress network, feeds can assign tickets to specific Zendesk Brand IDs.

5. Troubleshooting & Diagnostic Error Matrix

When ticket creation or user synchronization encounters issues, consult the following diagnostic matrix:

6. Developer Extensibility & Filter Hooks

Developers can programmatically modify ticket payloads or custom attributes prior to API transmission:

/**
 * Filter: gform_zendesk_ticket_payload
 * Purpose: Filter Zendesk ticket payload prior to API transmission.
 * 
 * @param array $ticket_payload The formatted API request body destined for Zendesk.
 * @param array $entry          The submitted Gravity Forms entry object.
 * @param array $form           The active form object.
 * @return array Modified ticket payload.
 */
add_filter( 'gform_zendesk_ticket_payload', function( $ticket_payload, $entry, $form ) {
    // Programmatically append referral metadata to ticket subject
    $ticket_payload['ticket']['subject'] = '[Web Inquiry] ' . $ticket_payload['ticket']['subject'];
    
    // Inject custom tags dynamically
    $ticket_payload['ticket']['tags'][] = 'gravityforms_sync';
    
    // Attach user IP to ticket metadata
    $ticket_payload['ticket']['metadata']['client_ip'] = rgar( $entry, 'ip' );
    
    return $ticket_payload;
}, 10, 3 );

/**
 * Action: gform_zendesk_post_ticket_create
 * Purpose: Save created Zendesk Ticket ID to entry metadata and log entry note.
 * 
 * @param array $response HTTP response returned from Zendesk REST API.
 * @param array $entry    The active Gravity Forms entry.
 * @param array $form     The form object.
 */
add_action( 'gform_zendesk_post_ticket_create', function( $response, $entry, $form ) {
    $body = json_decode( wp_remote_retrieve_body( $response ), true );
    if ( ! empty( $body['ticket']['id'] ) ) {
        $ticket_id = sanitize_text_field( $body['ticket']['id'] );
        gform_update_meta( $entry['id'], '_zendesk_ticket_id', $ticket_id );
        
        $note = sprintf( 'Zendesk Ticket #%s created successfully.', $ticket_id );
        GFFormsModel::add_note( $entry['id'], 0, 'Zendesk', $note );
    }
}, 10, 3 );

7. Frequently Asked Questions