Skip to main content

In Cartegraph, Material Logs can be associated with tasks. When the Cartegraph task activity is a certain type (example, snow removal), I want to use Zapier weather to add the weather to the materials section (I have the necessary fields on the Material Log side in Cartegraph). To accomplish, this I need to update an existing Material Log entry with the weather information. Any ideas?

Hi ​@NJohan 

Help us have more info by posting these screenshots and more details about the issue you are having:

  • how your Zap steps are outlined
  • how your Zap steps are configured in EDIT mode with the field mappings visible
  • any encountered errors testing Zap steps

Steps: find a Material log that was created or update, continue if it is not a stock transaction. Find a task with that has a corresponding Task ID to the Material Log and output coordinates. Past coordinates into weather by Zapier, and then update the Material Log with temp and wind speed. 

 

Have an issue here. All of the potential test records are the same log, and it is stock transaction, so automation can not be tested. 

 


@NJohan 

Zap trigger is instant via a webhook from Cartegraph, so you probably need to test the trigger event in Cartegraph after the Zap step is configured, then test the Zap trigger step to try to pull thru actual data from Cartegraph.

 

Otherwise, you can turn the Zap ON and test live.

Then check the Zap Runs: https://zapier.com/app/history/

How to use an existing Zap Run as a Zap trigger example: https://help.zapier.com/hc/en-us/articles/35632951078029-Use-previous-Zap-runs-as-trigger-test-records


@Troy Tessalone 

I have entered a new Material log, which should be the trigger event for the Zap (since the trigger is event create or update). The newly created record to test has not come through to be available to test in the Zap. It’s not letting me publish the Zap until the field mapping errors are fixed for the weather step, and I can not get the coordinates until I can force a new Material Log entry to be available to test on. 

Does that make sense? Kind of confusing. 


@NJohan 

You can put dummy data in required fields to get the Zap to be able to turn ON, so you can test live, then fix later.


@Troy Tessalone I put in dummy data for it try and force it to run. However, it is still not actually behaving recognizing when I create or update a record. Any further insight?

 


@NJohan 

Post updated screenshots for us to have current context.

Help us have more info by posting these screenshots and more details about the issue you are having:

  • how your Zap steps are outlined
  • how your Zap steps are configured in EDIT mode with the field mappings visible
  • any encountered errors testing Zap steps

I manually added some coordinates into the coordinates fields on the weather function so that I could publish it to try and force live data. I then went back to Cartegraph to create a new Material Log record, and when I click “Find new records,” it is not finding it. Additionally, the records that it has found are all actually the same (and not the new ones). 


@NJohan 

Did you turn the Zap ON and test live?

Then check your Zap Runs for activity? https://zapier.com/app/history/

Once you have Zap Run activity, follow this previously shared help link to get a real Zap Run to be used as the Zap trigger example record to help you configure your Zap action steps.

 

How to use an existing Zap Run as a Zap trigger example: https://help.zapier.com/hc/en-us/articles/35632951078029-Use-previous-Zap-runs-as-trigger-test-records


Hi ​@NJohan 👋

How are things progressing on this? Did using a live Zap run for the test record as Troy suggested allow you to get the Zap setup as needed?

Want to make sure this gets sorted, so please keep us in the loop on how it went!


Hi ​@SamB 

Yes, I was able to force a turn on after a few tries but got it working eventually. Thanks!


Reply