Has anyone used the FedEx Create Shipment action? In the connector reference, FedEx | Microsoft Power Automate, when I click on the documentation, it says it does not exist. I can add the connector to a workflow, but without documentation I am not sure how to configure it. Do you put the same body as if you were using an HTTP request?
I have a FedEx developer account and have been having trouble with using HTTP requests and thought this action would be easier to use and more reliable.
The following is how the top portion of the HTTP request is formatted:
Then this is the body:
"labelResponseOptions": "URL_ONLY",
"requestedShipment": {
"shipper": {
"contact": {
"personName": "@{items('Apply_to_each')?['ReportedBy']}",
"phoneNumber": @{items('Apply_to_each')?['Telephone']},
"companyName": "@{items('Apply_to_each')?['Name']}"
},
"address": {
"streetLines": [
"@{items('Apply_to_each')?['Street']}"
],
"city": "@{items('Apply_to_each')?['City']}",
"stateOrProvinceCode": "@{items('Apply_to_each')?['Region']}",
"postalCode": @{items('Apply_to_each')?['PostalCode']},
"countryCode": "US"
}
},
"recipients": [
{
"contact": {
"personName": "@{items('Apply_to_each')?['ReturnAttention']}",
"phoneNumber": 8005551212,
"companyName": "@{items('Apply_to_each')?['ReturnCompany']}"
},
"address": {
"streetLines": [
"@{items('Apply_to_each')?['ReturnStreet']}"
],
"city": "@{items('Apply_to_each')?['ReturnCity']}",
"stateOrProvinceCode": "@{items('Apply_to_each')?['ReturnState']}",
"postalCode": @{items('Apply_to_each')?['ReturnZIP']},
"countryCode": "US"
}
}
],
"shipDatestamp": "@{formatDateTime(utcNow(),'yyyy-MM-dd')}",
"serviceType": "FEDEX_GROUND",
"packagingType": "YOUR_PACKAGING",
"pickupType": "DROPOFF_AT_FEDEX_LOCATION",
"blockInsightVisibility": false,
"shippingChargesPayment": {
"paymentType": "SENDER"
},
"shipmentSpecialServices": {
"specialServiceTypes": [
"RETURN_SHIPMENT"
],
"returnShipmentDetail": {
"returnType": "PRINT_RETURN_LABEL"
}
},
"labelSpecification": {
"imageType": "PDF",
"labelStockType": "PAPER_85X11_TOP_HALF_LABEL"
},
"requestedPackageLineItems": [
{
"weight": {
"value": 10,
"units": "LB"
},
"dimensions": {
"length": 10,
"width": 10,
"height": 10,
"units": "IN"
},
"customerReferences": [
{
"customerReferenceType": "RMA_ASSOCIATION",
"value": "@{items('Apply_to_each')?['Document']}"
},
{
"customerReferenceType": "CUSTOMER_REFERENCE",
"value": "@{items('Apply_to_each')?['Description']}"
}
]
}
]
},
"accountNumber": {
"value": "your account number"
}
}
Keep in mind, this is specific to the shipment type we are sending, which is an RMA via FedEx Ground. If you are using a different service, they all have different requirements.
It results in a label that looks like this:
Good afternoon, we have currently set up a developer account, but we have made some unsuccessful attempts. Could you share the content from within your http that sends the request? Can you explain to me better what
"creating a solution in your developer environment"
I believe I have already configured the topics you mentioned above, but so far without success.
Maybe I have the structure that you used and had success, I can solve it...
Maybe, it is quite complicated and took me about six months to finally work out all the issues. Have you set up a developer account with FedEx? If not, that will need to be done first and then a solution will need to be created in their developer environment that has your company's correct information and the account that will be billed from the API calls. For each billing account, you'll need a separate solution. If you have all that, is there a specific action you are having trouble with?
I have only figured this out for shipping an RMA through FedEx Ground.
WarrenBelz
146,776
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
66,093
Most Valuable Professional