Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Google Cloud Application Integration – API Trigger to Connector Task: "Connector input payload not p

 

I'm building an integration using Google Cloud Application Integration to fetch the content of a Google Drive file using its fileId.

I have an API Trigger with input variable fileid.

A Connectors task uses the Google Drive connector with the action: GET_files/%7BfileId%7D → expecting the value in Path parameters.fileId.

Problem: Even when providing fileid via the API Trigger, the integration fails with the error:

Required parameter Connector input payload is not present.

What I need help with: How can I correctly map the fileid input from the API Trigger to the Connector task input (Path parameters.fileId) so the request succeeds?

Is there something specific required to pass the input to connectorInputPayload?

Solved Solved
0 1 73
1 ACCEPTED SOLUTION

Hi @oumaima,

Welcome to Google Cloud Community!

First, can you confirm that your Google Drive connector and authentication are set up correctly? It’s worth double-checking against this documentation to rule out any config issues.

Next, for the GET operation, keep in mind that it’s meant to retrieve a single record using a primary key—in this case, that would be the fileId. If you’re trying to search more broadly, you’d want to use the List operation with a filterClause instead.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

View solution in original post

1 REPLY 1

Hi @oumaima,

Welcome to Google Cloud Community!

First, can you confirm that your Google Drive connector and authentication are set up correctly? It’s worth double-checking against this documentation to rule out any config issues.

Next, for the GET operation, keep in mind that it’s meant to retrieve a single record using a primary key—in this case, that would be the fileId. If you’re trying to search more broadly, you’d want to use the List operation with a filterClause instead.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

Top Solution Authors