FAIR

Federated and Independent Repositories

EDSA FieldTrack Connector

Plugin Banner

EDSA FieldTrack Connector

by edsadev

Download
Description

EDSA FieldTrack Connector helps WordPress site owners collect service requests from their website, review those requests inside WordPress, and send approved requests into EDSA FieldTrack as work orders.

This plugin is a connector for the paid EDSA FieldTrack service. WordPress can collect and store requests locally after installation, but FieldTrack sync, work-order creation, and FieldTrack status tracking require an active EDSA FieldTrack subscription, tenant ID, and connector token.

The connector is intentionally lightweight. It does not duplicate the full FieldTrack back office inside WordPress. Instead, it:

  • Adds a FieldTrack settings page in WordPress.
  • Provides the [edsafico_request_form] shortcode.
  • Stores customer service requests in a local WordPress request inbox.
  • Lets admins choose which FieldTrack-mapped form fields appear on the request form.
  • Lets admins add custom intake fields that sync to FieldTrack internal notes.
  • Lets admins customize service type choices.
  • Supports optional photo/document uploads.
  • Supports optional Cloudflare Turnstile or Google reCAPTCHA v2 spam protection.
  • Provides editable admin and customer email templates.
  • Gives admins request statuses for new, reviewed, sent, failed, duplicate, and rejected requests.
  • Lets admins manually send or retry a reviewed request to FieldTrack.
  • Can automatically create a FieldTrack work order after submission.
  • Stores FieldTrack sync status, sync logs, and returned work-order keys on the WordPress request.
  • Can refresh the latest FieldTrack work-order status after sync, including via WP-Cron.

Paid Service Requirement

This plugin connects to EDSA FieldTrack, a paid external service operated by EDSA. To use FieldTrack sync features, the site owner must have:

  • An active EDSA FieldTrack subscription.
  • A FieldTrack tenant ID.
  • A WordPress connector token generated inside EDSA FieldTrack.

Without those credentials, the plugin can still display a WordPress service request form and store requests locally, but it cannot create FieldTrack work orders or refresh FieldTrack work-order status.

External Services

This plugin connects to EDSA FieldTrack services operated by EDSA when the site owner configures a FieldTrack service URL, tenant ID, and connector token.

By default, requests are sent to:

https://www.edsa.dev/core/api/public/fieldtrack/service-requests/

Synced work-order statuses are refreshed from:

https://www.edsa.dev/core/api/public/fieldtrack/work-orders/status/

The plugin sends request data only when the site owner tests the connection, manually syncs a request, enables automatic sync, or enables automatic status refresh for previously synced requests.

Data sent to EDSA FieldTrack may include:

  • FieldTrack tenant ID.
  • Connector token.
  • Customer name.
  • Customer email.
  • Customer phone.
  • Service address.
  • Service type.
  • Request title.
  • Request details / work order description.
  • Preferred service date.
  • Source page URL.
  • Uploaded attachment URLs stored in WordPress.
  • Custom WordPress intake fields, sent as FieldTrack internal notes.
  • FieldTrack work-order ID or work-order key when refreshing status.

If Cloudflare Turnstile or Google reCAPTCHA v2 is enabled by the site owner, the visitor’s spam verification token is sent to the selected spam protection provider for validation.

EDSA policies:

  • Privacy Policy: https://www.edsa.dev/privacy-policy/
  • Terms of Service: https://www.edsa.dev/terms-of-use/

Third-party spam protection policies:

  • Cloudflare Turnstile Privacy Policy: https://www.cloudflare.com/privacypolicy/
  • Cloudflare Terms: https://www.cloudflare.com/website-terms/
  • Google Privacy Policy: https://policies.google.com/privacy
  • Google Terms: https://policies.google.com/terms

Privacy

This plugin may process personal information submitted through a WordPress service request form. Site owners are responsible for informing visitors that submitted service request information may be stored in WordPress and, when FieldTrack sync is enabled or manually used, sent to EDSA FieldTrack.

The plugin stores submitted requests in WordPress as private FieldTrack request records. Uploaded files are stored in the WordPress media system as private attachments where supported by WordPress. Synced requests are sent to EDSA FieldTrack using the configured tenant ID and connector token.

Site owners should update their own privacy policy to explain their use of this connector, EDSA FieldTrack, and any enabled spam protection provider.

  1. Upload the edsa-fieldtrack-connector folder to /wp-content/plugins/.
  2. Activate the plugin through the WordPress Plugins screen.
  3. Subscribe to EDSA FieldTrack if you do not already have an active FieldTrack subscription.
  4. In EDSA FieldTrack, open Customer Portal and generate a WordPress connector token.
  5. In WordPress, go to FieldTrack > Settings.
  6. Enter the FieldTrack service URL, tenant ID, and connector token.
  7. Test the connection.
  8. Configure form fields, service type choices, email templates, and spam protection as needed.
  9. Add [edsafico_request_form] to the page where customers should request service.
Is an EDSA FieldTrack subscription required?

The WordPress connector plugin can be installed in WordPress, but FieldTrack sync features require an active paid EDSA FieldTrack subscription. Without a subscription, tenant ID, and connector token, requests can be stored locally in WordPress but cannot be synced into FieldTrack.

Does this replace FieldTrack?

No. WordPress handles intake and review. EDSA FieldTrack remains the operational system for work orders, technicians, customers, invoices, payments, status tracking, and reporting.

Can I review requests before they become work orders?

Yes. Leave automatic sync disabled. Requests will appear in WordPress under FieldTrack > Requests, where an admin can review and send them to FieldTrack.

Can requests create work orders automatically?

Yes. Enable automatic sync in FieldTrack > Settings. Automatic sync requires a valid FieldTrack tenant ID and connector token.

Can I control which fields appear on the form?

Yes. FieldTrack > Settings lets admins show, hide, require, and relabel FieldTrack-mapped fields. Admins can also add custom fields that are saved in WordPress and sent to FieldTrack as internal notes.

Does the plugin send customer data to EDSA?

Yes, when FieldTrack sync is used. The plugin sends service request details to the configured EDSA FieldTrack service URL so FieldTrack can create or track work orders for the configured tenant.

How do I subscribe to FieldTrack?

Use the Subscribe to FieldTrack button on the plugin settings screen, choose a CORE FieldTrack package, complete checkout, then generate the connector token from FieldTrack.

0.2.1

  • Updated the WordPress.org contributor username.
  • Moved public form styles and spam-provider scripts to WordPress enqueue APIs.
  • Replaced generic plugin-owned identifiers and shortcode names with the unique edsafico prefix.

0.2.0

  • Clarified that FieldTrack sync requires a paid EDSA FieldTrack subscription.
  • Added configurable FieldTrack-mapped form fields.
  • Added custom intake fields that sync into FieldTrack internal notes.
  • Added configurable service type choices.
  • Added optional Cloudflare Turnstile and Google reCAPTCHA v2 spam protection.
  • Added editable admin and customer email templates.
  • Added sync retry labeling and recent sync logs.
  • Added automatic status refresh using WP-Cron.
  • Expanded privacy and external service disclosures.

0.1.0

  • Initial lightweight FieldTrack connector.
  • Added service request shortcode.
  • Added local WordPress request inbox.
  • Added manual and automatic FieldTrack work-order sync.
  • Added FieldTrack connector token connection test.
  • Added request review statuses and FieldTrack status refresh support.
Back to top