What It Does
When your team closes a deal in Pylon and the customer e-signs a
proposal, Worx Safety automatically creates a new project with all
the customer and site details — no double entry, no copy-paste
errors. Every signed proposal becomes a job-ready project in Worx
within seconds.
What Gets Synced
When a customer signs a proposal in Pylon, the following details
flow into Worx Safety automatically:
- Project name — built from the Pylon reference number and customer name
- Customer details — name, phone number, and email
- Site address — full street address, city, state, postcode, and country
- Site map — the address is geocoded and a map pin is attached to the project
Each synced project is linked back to its Pylon source, so there are
never duplicates — even if Pylon sends the same event more than
once.
How to Connect
Setting up the integration takes a few minutes and only needs to be
done once. You'll need admin access to both Pylon and Worx Safety.
Step 1 — Add Your Pylon API Token
2. In Worx Safety, go to Integrations -> Pylon and enter the token.
3. Worx will test the connection immediately — you'll see a
confirmation if it's working.
Step 2 — Set Up the Webhook
1. Worx Safety generates a unique webhook URL for your account —
copy it from the setup screen.
destination using that URL.
3. Subscribe to the solar_projects.updated and web_proposals.signed events.
Step 3 — Enter the Webhook Secret
1. When Pylon creates the webhook, it gives you a signing secret.
2. Paste that secret back into Worx Safety on the same setup screen.
3. You're done — the link is live.
What Happens Next
Once connected, the process is fully automatic:
1. A customer e-signs a proposal in Pylon.
2. Pylon notifies Worx Safety within seconds.
3. Worx Safety pulls the full project details from Pylon.
4. A new project is created in Worx with all customer info, site
address, and a map pin — ready for scheduling.
There's nothing to click, no import to run, and no sync to trigger.
It just works in the background.
Default Settings
During setup you can configure a default project manager name and
phone number. Every project that comes in from Pylon will be
assigned to that manager automatically, so your team knows who's
responsible from the moment a deal is signed.
Reliability & Security
- No duplicates — If the same project comes through more than once, Worx recognises it and skips the duplicate.
- Automatic retries — If there's a temporary network issue, Worx retries the sync automatically so nothing is missed.
- Encrypted credentials — Your Pylon API token and webhook secret are encrypted at rest. They are never stored in plain text.
- Signed webhooks — Every incoming event is cryptographically verified to ensure it genuinely came from Pylon.
Frequently Asked Questions
Can I disconnect Pylon later?
Yes. Go to Integrations -> Pylon -> Disconnect in Worx Safety to remove the
connection at any time. Existing projects are not affected.
What if a project was already created manually?
Worx uses the Pylon project ID to check for duplicates. If a
matching project already exists, it won't create a second one.
Does it sync changes after the initial creation?
The integration creates projects when proposals are signed. If
project details are updated in Pylon afterwards, Worx receives the
event but will not overwrite a project that already exists.
What if the customer hasn't accepted the proposal yet?
Worx only creates projects for accepted proposals. Unsigned or
pending proposals are ignored until the customer signs.
To get started, reach out to your Worx Safety administrator and have
your Pylon API credentials ready. Setup takes less than five
minutes.