Hi @Gonzalo Arellano 

Good question.

To help give us more context, please post detailed screenshots with how the Zap steps are configured, thanks.

These are the zap screenshots:
1-The trigger: Company updated or created in hubspot. This return a several properties each time the company is updated or created in hubspot and it works perfectly. 
 

2- The second step is Run Javascript in code. I use this step to send the required prop “MessageGroupId” in the next step (but it didn’t work   ).  

3 - The last step is to use Create message in amazon sqs, I select the fifo queue (previously created), I add in content the previous data returned in step 2 and encoding base64. But this always return error

This error
 

@Gonzalo Arellano 

Try removing the “1” so it’s just 1.

JavaScript Code example: https://help.zapier.com/hc/en-us/articles/8496197098253-JavaScript-code-examples-in-Zaps

@Gonzalo Arellano

Try removing the “1” so it’s just 1.

 

JavaScript Code example: https://help.zapier.com/hc/en-us/articles/8496197098253-JavaScript-code-examples-in-Zaps

That didn’t work either.  I don’t know how zappier takes the “Content“ value, I mean the content is the value for MessageBody for sqs? and that could be the reason why is not taking the MessageGroupId?    

@Gonzalo Arellano 

Help article to reference: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SendMessage.html

Thank you! But I still have the same question, how can I pass MessageGroupId in the sqs step in zappier?

@Gonzalo Arellano 

You’ll need to reference the help article for how to configure the JSON: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SendMessage.html

MessageGroupId

This parameter applies only to FIFO (first-in-first-out) queues.

The tag that specifies that a message belongs to a specific message group. Messages that belong to the same message group are processed in a FIFO manner (however, messages in different message groups might be processed out of order). To interleave multiple ordered streams within a single queue, use MessageGroupId values (for example, session data for multiple users). In this scenario, multiple consumers can process the queue, but the session data of each user is processed in a FIFO fashion.

The length of MessageGroupId is 128 characters. Valid values: alphanumeric characters and punctuation (!"#$%&'()*+,-./:;<=>?@g\]^_`{|}~).

For best practices of using MessageGroupId, see Using the MessageGroupId Property in the Amazon SQS Developer Guide.

Type: String

Required: No

@Gonzalo Arellano

You’ll need to reference the help article for how to configure the JSON: https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_SendMessage.html

 

 

MessageGroupId

This parameter applies only to FIFO (first-in-first-out) queues.

The tag that specifies that a message belongs to a specific message group. Messages that belong to the same message group are processed in a FIFO manner (however, messages in different message groups might be processed out of order). To interleave multiple ordered streams within a single queue, use MessageGroupId values (for example, session data for multiple users). In this scenario, multiple consumers can process the queue, but the session data of each user is processed in a FIFO fashion.

• You must associate a non-empty MessageGroupId with a message. If you don't provide a MessageGroupId, the action fails.

• ReceiveMessage might return messages with multiple MessageGroupId values. For each MessageGroupId, the messages are sorted by time sent. The caller can't specify a MessageGroupId.

The length of MessageGroupId is 128 characters. Valid values: alphanumeric characters and punctuation (!"#$%&'()*+,-./:;<=>?@t\]^_`{|}~).

For best practices of using MessageGroupId, see Using the MessageGroupId Property in the Amazon SQS Developer Guide.

Important

MessageGroupId is required for FIFO queues. You can't use it for Standard queues.

Type: String

Required: No

I am already sending the required data but the zap continues throwing the same error.
 

@Gonzalo Arellano 

If you have a Zapier paid plan, you can open a ticket with Zapier Support: https://zapier.com/app/get-help